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: Fri, 21 Oct 2005 14:08:20 +0300	[thread overview]
Message-ID: <4358CC24.6020404@gentoo.org> (raw)
In-Reply-To: <4358BB36.1090902@gentoo.org>

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

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?
> Current rules say that /etc/portage/package.use overrides make.conf, and
> user config overrides profiles, the proposal would create a new
> unintuitive situation between those two.
> Depending on the answer on this it also has some technical implications
> with the way package.use support is implemented currently. In short it's
>  not a trivial thing to do.
> 
> Marius

Gentoo being about choice the new package.use should come before
anything user set. I do not see any problem with this if it works in the
same way as package.mask already works. Please, enlighten me.

Regards,
Petteri Räty


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

  reply	other threads:[~2005-10-21 11:11 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 [this message]
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=4358CC24.6020404@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