From: Jason Stubbs <jasonbstubbs@mailandnews.com>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] The purpose of USE flags
Date: Tue, 16 Dec 2003 18:19:52 +0900 [thread overview]
Message-ID: <200312161819.52882.jasonbstubbs@mailandnews.com> (raw)
In-Reply-To: <200312130427.00785.jasonbstubbs@mailandnews.com>
On Saturday 13 December 2003 04:27, Jason Stubbs wrote:
> I've been thinking on the idea of USE flags and am wondering what the
> developers' perspective is. They are defined in "Gentoo Guide to USE flags"
> as "keywords that define options used on a system-wide basis to configure
> applications during their respective compilation procedures". Is there any
> other, more formal, definition?
Well, seeing there was no negative (read: any) feedback, I will summarize the
motivation for this as a new requirement. Something to the effect of:
The meaning and function of USE flags should be immediately apparent to users
regardless of their technical skill. This applies to individual USE flags,
USE flags with respect to individual applications and also with respect to
the system as a whole.
--
Regards,
Jason Stubbs
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-12-16 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 19:27 [gentoo-portage-dev] The purpose of USE flags Jason Stubbs
2003-12-14 19:24 ` Sami Näätänen
2003-12-14 22:23 ` Marius Mauch
2003-12-16 9:38 ` Jason Stubbs
2003-12-16 17:11 ` Sami Näätänen
2003-12-16 19:59 ` Marius Mauch
2003-12-16 21:50 ` Sami Näätänen
2003-12-16 22:23 ` Jason Stubbs
2003-12-17 0:10 ` Marius Mauch
2003-12-17 7:11 ` Jason Stubbs
2003-12-16 21:36 ` Pieter Van den Abeele
2003-12-16 22:23 ` Paul de Vrieze
2003-12-16 22:53 ` Pieter Van den Abeele
2003-12-16 9:19 ` Jason Stubbs [this message]
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=200312161819.52882.jasonbstubbs@mailandnews.com \
--to=jasonbstubbs@mailandnews.com \
--cc=gentoo-portage-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