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 01:11:06 +0300	[thread overview]
Message-ID: <435815FA.1040508@gentoo.org> (raw)
In-Reply-To: <200510210000.04554.danarmak@gentoo.org>

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

Dan Armak wrote:
> On Thursday 20 October 2005 23:47, 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.
> 
> Because implementing https://bugs.gentoo.org/show_bug.cgi?id=61732 would be a 
> lot more cool :-)

Cool indeed. I did a quick search on bugzilla for package.use, but did
not find out anything. Although I was quite sure that something like
this was already proposed, but searching for my solution did not bring
anything up.

> 
> Besides, if the effect on portage's behavior is the same, what's the 
> difference?
> 

Well my solution is backwards compatible because older portage versions
will just ignore the file. The solution in the bug would need the new
EAPI stuff which is probably still some time away (just a guess). The
package.use file could be used in the meantime and after the new
features are available we could just move everything from the
package.use file to the ebuilds themselves.

Regards,
Petteri


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

  reply	other threads:[~2005-10-20 22:12 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 [this message]
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
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=435815FA.1040508@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