public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ${PORTDIR}/profiles/package.use
Date: Thu, 20 Oct 2005 22:55:20 -0400	[thread overview]
Message-ID: <200510202255.20547.vapier@gentoo.org> (raw)
In-Reply-To: <435856DB.4080206@egr.msu.edu>

On Thursday 20 October 2005 10:47 pm, Alec Warner wrote:
> Mike Frysinger wrote:
> > On Thursday 20 October 2005 10:03 pm, Alec Warner wrote:
> >>Mike Frysinger wrote:
> >>>On Thursday 20 October 2005 05:47 pm, Petteri Räty wrote:
> >>>>Every once in a while I see people wanting to use nosomething use
> >>>> flags. Why don't we have a package.use like we already have a
> >>>> package.mask file? This would make it possible for developers to turn
> >>>> on use flags by default in a way that would not cruft the base
> >>>> profiles for every local use flag.
> >>>
> >>>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.
> >><snip>
> >
> > 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
>
> And we should keep the current shitty behavior to accomediate cxx why?
> What is so hard about USE="-* cxx"?  Are there no other flags that do
> bad things when they aren't turned on via use.defaults and profiles?

i only said keep nocxx

there is nothing hard about USE="-* cxx" but while most here want to say 'fuck 
the users' (and i'm inclined to agree), i'd rather not field those 
bugs/questions/etc...
-mike

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-10-21  2:55 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         ` [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 [this message]
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=200510202255.20547.vapier@gentoo.org \
    --to=vapier@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