public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting: Tuesday 14 August 2012, 19:00 UTC
Date: Wed, 26 Sep 2012 16:16:04 -0700	[thread overview]
Message-ID: <20120926231604.GK26094@localhost> (raw)
In-Reply-To: <CALc3eMXqgP2xBJs9zDQu0qCi-4jAvpyB-B89p6nG2wU5zK0L+Q@mail.gmail.com>

On Sat, Sep 08, 2012 at 02:12:40PM +0100, David Leverton wrote:
> On 14 August 2012 23:20, Micha?? G??rny <mgorny@gentoo.org> wrote:
> > On Tue, 14 Aug 2012 23:02:04 +0100
> > Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> >> There's still the issue that we haven't decided what [use] deps do
> >> when they show up in profile files. We were sticking at 1 until we
> >> worked that out.
> >
> > Ah, about that. It will be useful if [use] deps in package.mask worked
> > unlike in package.use.mask, thus giving us a tool to temporarily mask
> > packages which are broken only with given flags.
> 
> Do we have a verdict on this?  What Micha?? suggests for package.mask
> sounds OK to me, but use deps in package.use, package.use.mask, etc
> could be rather nastier, and I'd be inclined to ban those unless
> someone has a better idea.

Use deps in all *.mask are already banned; whether by spec or 
convention- when they were added the potential was known, and stated 
as "don't do that".

If we're going to try doing it now, analysis needs to be done to see 
what fallout there is *before trying to change the fucking thing*.

Offhand, I'd strongly bet no PM will handle a use dep atom in 
package.mask now; as for *.use.* abuse of use deps, that's frankly 
worse- it's chained deps, "if this use configuration, mask that flag".  
That's hell on wheels for the PM to implement.

Personally, I'd like to see 'dev-util/diffball[debug]' usable in 
package.use.mask (instead of dev-util/diffball debug), but it's not a 
backwards compatible change w/ existing PMs.

Either way, the verdict is "can't go anywhere till compatibility is 
figured out" :P

~harring


  reply	other threads:[~2012-09-27  0:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 19:17 [gentoo-project] Council meeting: Tuesday 14 August 2012, 19:00 UTC Fabian Groffen
2012-08-12 21:05 ` Ulrich Mueller
2012-08-12 21:13   ` Michał Górny
2012-08-13  7:41   ` hasufell
2012-08-14  7:02   ` Arfrever Frehtes Taifersar Arahesis
2012-08-14  9:24     ` Ciaran McCreesh
2012-08-14  8:15   ` Michał Górny
2012-08-14  9:02   ` Zac Medico
2012-08-14 14:01   ` Ulrich Mueller
2012-08-14 16:09     ` Richard Yao
2012-08-14 16:42       ` Richard Yao
2012-08-14 21:17     ` Andreas K. Huettel
2012-08-14 21:35       ` Ciaran McCreesh
2012-08-14 21:55         ` Zac Medico
2012-08-14 22:02           ` Ciaran McCreesh
2012-08-14 22:14             ` Zac Medico
2012-08-14 22:20             ` Michał Górny
     [not found]               ` <20120815130131.1a3f10a8@googlemail.com>
2012-08-15 12:11                 ` Michał Górny
2012-08-15 12:12                   ` Ciaran McCreesh
2012-08-15 12:23                     ` Michał Górny
2012-09-08 13:12               ` David Leverton
2012-09-26 23:16                 ` Brian Harring [this message]
2012-08-14 22:21           ` Andreas K. Huettel
2012-08-14 22:29             ` Zac Medico
2012-08-26 11:37 ` [gentoo-project] Council meeting summary: " Fabian Groffen

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=20120926231604.GK26094@localhost \
    --to=ferringb@gmail.com \
    --cc=gentoo-project@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