From: "Spider (D.m.D. Lj.)" <spider@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ${PORTDIR}/profiles/package.use
Date: Fri, 21 Oct 2005 04:34:22 +0200 [thread overview]
Message-ID: <1129862062.1653.1.camel@Darkmere.darkmere> (raw)
In-Reply-To: <200510202226.58360.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
On Thu, 2005-10-20 at 22:26 -0400, Mike Frysinger wrote:
> On Thursday 20 October 2005 10:19 pm, Dave Nebinger wrote:
> > >> > 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?
>
> you're missing the fact that if we change 'nocxx' to 'cxx' then everyone who
> uses '-*' in their USE flags will emerge their gcc without C++ support
> -mike
Yes. And that is as intended with -*.
Really, Don't refuse an idea because this. Having IUSE="cxx" USE="-*"
and getting -cxx is expected behaviour.
Not having a C++ compiler might be just exactly what they want,
right? :)
//Spider
--
begin .signature
Tortured users / Laughing in pain
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-21 2:36 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.) [this message]
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 ` [gentoo-dev] ${PORTDIR}/profiles/package.use Duncan
2005-10-21 11:51 ` 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=1129862062.1653.1.camel@Darkmere.darkmere \
--to=spider@gentoo.org \
--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