From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Stroller <root@stellar.eclipse.co.uk>
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: Use of USE flags..? Was: Re: [gentoo-dev] Enemy Territory ebuild
Date: Tue, 21 Oct 2003 16:23:10 -0400 [thread overview]
Message-ID: <1066767790.31734.9.camel@localhost> (raw)
In-Reply-To: <893C9795-03ED-11D8-AF70-000A95795F3E@stellar.eclipse.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2741 bytes --]
On Tue, 2003-10-21 at 13:39, Stroller wrote:
> On Oct 21, 2003, at 2:15 pm, Chris Gianelloni wrote:
> >
> > I would definitely *not* use a USE flags at all, since a USE flag is
> > for
> > adding or removing optional features from a package. If anything were
> > to be used, it would be a FEATURE flag.
>
> I am aware of the -devs attitude towards USE-flag bloat, and my
> original posting "you can never have too many USE flags" was intended
> as a joke (obviously a very poor one). However, from a user perspective
> USE flags are quite desirable - they keep all options in one place, I
> can `emerge -vp someapp` & easily use `ufed` to determine what each
> flag means & change it as required.
However, a USE flag has a specific function and should stay that way to
keep confusion down. There are already a few cases where USE flags are
used to do things they shouldn't be.
> You say that "a USE flag is for adding or removing optional features
> from a package", however I am not really clear what this means. My
> recent experimentation, for instance, with the prelinking & the "pic"
> USE flag seems to indicate that "-fPIC" will be added to the user's
> CFLAGS. But only, I think, if the package supports prelinking..?
The -fPIC is actually used to enable PIC support in applications. For
example, if you were to have -fPIC in your CFLAGS, there are some
packages that will NOT compile. The pic USE flag is for enabling -fPIC
in a way which is suitable to the package. It isn't just tacking
"-fPIC" onto your CFLAGS and that's it. In many cases it requires
patches to the source, which aren't needed when not compiling with
-fPIC.
> Having USE flags change CFLAGS seems to me to be non-intuitive, and I
> don't really see how a "patches" USE flag is any different from the
> existing "mmx", "oss", or (to be honest) any other USE flags.
Let's take... a fictional game I would like to call GentooRulez.
GentooRulez can use mmx, but only if it is added on the ./configure line
with a --enable-mmx. Otherwise, it builds without. This is the prime
example of when to use the mmx USE flag.
Now, a new version of GentooRulez comes out and you want to merge it
using patches. You are wanting to tell PORTAGE itself to use patches.
It makes no changes to the actual configuration/build. FEATURES control
portage itself. USE flags control the package compilation/install
options.
> Could someone be so kind as to explain when a USE flag should & should
> not be used, and what is the difference between USE flags & FEATUREs..?
>
> Many thanks,
>
> Stroller.
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a pengiun?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-10-21 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 13:30 [gentoo-dev] Enemy Territory ebuild Chris Gianelloni
2003-10-18 18:13 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2003-10-18 19:27 ` [gentoo-dev] " Matt Thrailkill
2003-10-18 21:53 ` Mike Frysinger
2003-10-19 0:08 ` Luke-Jr
2003-10-20 7:48 ` Matt Thrailkill
2003-10-18 19:39 ` Stroller
2003-10-19 13:31 ` Corvus Corax
2003-10-19 14:01 ` Chris Gianelloni
2003-10-20 6:06 ` Mike Frysinger
[not found] ` <B6AD5486-01A2-11D8-A06D-000A95795F3E@stellar.eclipse.co.uk>
2003-10-19 13:52 ` Chris Gianelloni
2003-10-21 12:39 ` Dhruba Bandopadhyay
2003-10-21 13:15 ` Chris Gianelloni
[not found] ` <893C9795-03ED-11D8-AF70-000A95795F3E@stellar.eclipse.co.uk>
2003-10-21 20:23 ` Chris Gianelloni [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=1066767790.31734.9.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=root@stellar.eclipse.co.uk \
/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