From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: ${PORTDIR}/profiles/package.use
Date: Fri, 21 Oct 2005 04:37:16 -0700 [thread overview]
Message-ID: <pan.2005.10.21.11.37.14.841665@cox.net> (raw)
In-Reply-To: 36596.127.0.0.1.1129861153.squirrel@cornholio
Dave Nebinger posted <36596.127.0.0.1.1129861153.squirrel@cornholio>,
excerpted below, on Thu, 20 Oct 2005 22:19:13 -0400:
>>> > i still dont see how this addresses the nocxx / USE=-*
>>>
>>> noFOO is used because "FOO" is on by default, and noFOO turns it off.
>>> AutoUSE is the same way, package bar is included in the buildplan and to
>>> have sane defaults, certain flags are turned on.
>>
>> that was a great explanation however irrelevant it may have been
>>
>> i guess we will have to make 'nocxx' a special case as we strip all other
>> 'no*' USE flags from portage
>
> Sorry, guys, but isn't that what "-FOO" is supposed to be for? If we
> already have support for "-FOO", why then do we need a "noFOO" also?
>
> Or is there some distinction I'm missing here?
Also consider the case of media-libs/libsdl. It uses novideo, noaudio,
and nojoystick, for the simple reason that for the vast majority of folks
who'd have reason to merge the package, turning OFF that functionality
makes entirely NO sense and having it OFF by default, if the USE flags
weren't enabled for some reason, would be entirely unintuitive.
Put another way... It is said over and over again that USE flags cover
OPTIONAL functionality. Few would consider video/audio/joystick support
in a library with a primary use of supporting games as optional. Rather,
the "option" would be to /not/ have support compiled in, and that's
/exactly/ what the no* USE flags express in this case, just as it's
/exactly/ what the nocxx USE flag expresses. Doing it any other way is,
as stated, counterintuitive to the way portage normally works, and the
defined use of USE flags.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-21 11:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 21:47 [gentoo-dev] ${PORTDIR}/profiles/package.use Petteri Räty
2005-10-20 22:00 ` Dan Armak
2005-10-20 22:11 ` Petteri Räty
2005-10-21 1:46 ` Mike Frysinger
2005-10-21 2:03 ` Alec Warner
2005-10-21 2:16 ` Mike Frysinger
2005-10-21 2:19 ` Dave Nebinger
2005-10-21 2:26 ` Mike Frysinger
2005-10-21 2:34 ` Spider (D.m.D. Lj.)
2005-10-21 2:43 ` Mike Frysinger
2005-10-21 2:49 ` Dan Meltzer
2005-10-21 2:56 ` Mike Frysinger
2005-10-21 6:44 ` Harald van Dijk
2005-10-21 13:10 ` Mike Frysinger
2005-10-21 17:23 ` Michiel de Bruijne
2005-10-21 23:58 ` Mike Frysinger
2005-10-21 11:37 ` Duncan [this message]
2005-10-21 11:51 ` [gentoo-dev] ${PORTDIR}/profiles/package.use Ciaran McCreesh
2005-10-23 12:24 ` Re[2]: " Jakub Moc
2005-10-21 17:53 ` Petteri Räty
2005-10-21 2:47 ` [gentoo-dev] ${PORTDIR}/profiles/package.use Alec Warner
2005-10-21 2:55 ` Mike Frysinger
2005-10-21 3:09 ` Dave Nebinger
2005-10-21 3:20 ` Dave Nebinger
2005-10-21 3:43 ` Chris Lee
2005-10-21 9:56 ` Marius Mauch
2005-10-21 11:08 ` Petteri Räty
2005-10-21 14:49 ` Marius Mauch
2005-10-21 15:58 ` Daniel Ostrow
2005-10-21 13:13 ` Mike Frysinger
2005-10-22 9:04 ` Petteri Räty
2005-10-22 9:05 ` Petteri Räty
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=pan.2005.10.21.11.37.14.841665@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.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