From: Terje Kvernes <terjekv@math.uio.no>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE flags and your annoyances
Date: 11 Apr 2003 03:39:12 +0200 [thread overview]
Message-ID: <wxx1y09g6db.fsf@nommo.uio.no> (raw)
In-Reply-To: <20030410143645.06a7b920.seemant@gentoo.org>
Seemant Kulleen <seemant@gentoo.org> writes:
[ ... ]
> As for which packages make use of which USE flags and for what
> purposes: I am redoing the USE howto, and hope to have that sort of
> thing extensively documented.
the bottom line here is that the documentation needs to be read.
make a _good_ point of this in the install-docs, pointing to the
USE-docs and saying "_read this_" might help.
> If anyone has productive ideas about how to improve it, please let
> us know. No offense, but bitching about things and making empty
> complaints is just trollbait.
indeed. USE is a great feature of Gentoo.
--
Terje
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-11 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 21:36 [gentoo-dev] USE flags and your annoyances Seemant Kulleen
2003-04-11 1:39 ` Terje Kvernes [this message]
2003-04-11 11:35 ` Fernand Albarracin
2003-04-14 2:49 ` Abhishek Amit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wxx1y09g6db.fsf@nommo.uio.no \
--to=terjekv@math.uio.no \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox