public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ${PORTDIR}/profiles/package.use
Date: Sat, 22 Oct 2005 12:04:11 +0300	[thread overview]
Message-ID: <435A008B.2010202@gentoo.org> (raw)
In-Reply-To: <200510210913.29341.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]

Mike Frysinger wrote:
> On Friday 21 October 2005 05:56 am, Marius Mauch wrote:
> 
>>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.
>>
>>The main problem I'd have with this is the stacking order, e.g.
>>profiles/package.use has "app-misc/foo bar" and make.conf has
>>"USE=-bar", which one should be preferred?
> 
> 
> this is a no brainer
> 
> profile use.defaults
> profile package.use
> profile make.defaults
> user make.conf
> user package.use
> user env
> -mike
> 

I think profile package.use should come after make.defaults. After all
package.use is package specific while make.defauls being generic. Of
course it should not matter if we make it a policy that people can't
turn off global use flags that are on by default on a per package basis,
but I would like this possibility. For example there is the python use
flag which is not needed with every package but there are packages that
need the python use flag for some dependencies. Maybe this was not the
best example but hopefully got the idea across. Of course this will be
fixed when the new portage will come this way some day.

Regads,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-10-22  9:06 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
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 [this message]
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=435A008B.2010202@gentoo.org \
    --to=betelgeuse@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