From: "Elfyn McBratney" <elfyn.mcbratney@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-core] Re: [gentoo-dev] Global USE flags bite the dust...
Date: Wed, 6 Sep 2006 11:18:43 +0100 [thread overview]
Message-ID: <92c39da00609060318y58af2191tdbca115ed346896@mail.gmail.com> (raw)
In-Reply-To: <92c39da00609060307m62f46ffchca980cd8b0bee43@mail.gmail.com>
Bah... this is really the last time I shall reply to myself!
> [...]
> On 06/09/06, Alin Nastac <mrness@gentoo.org> wrote:
> > Doug Goldstein wrote:
> > > dba
> > > dio
> > > ingres
> > > msession
> > > mcve
> > >
> > > are all used by 1 ebuild... and that's dev-lang/php... they should be
> > > moved to local's.
> > >
> > Consequence: php eclasses code should be moved in dev-lang/php ebuild.
>
> Erm, and duplicate USE flag detection code (thinks conflicts that
> portage still cannot handle... sigh) in every PHP ebuilds? No thanks!
> Easing maintainability is a good thing, ya know :P
This is wrong. Regardless of local to global, and vice versa, this
will not change the USE flag conflict detection. However, some of
these flags are used elsewhere (as Stu has already noted), and I think
since they've been around a while, and can easily be used by other
new/old packages without changes to profiles/use.local.desc, they
should stay where they are (global).
Best,
Elfyn
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-06 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 6:02 [gentoo-dev] Global USE flags bite the dust Doug Goldstein
2006-09-06 6:09 ` Donnie Berkholz
2006-09-06 6:35 ` [gentoo-core] " Doug Goldstein
2006-09-06 7:00 ` Alin Nastac
2006-09-06 8:48 ` Stuart Herbert
2006-09-06 10:04 ` Elfyn McBratney
2006-09-06 10:07 ` Elfyn McBratney
2006-09-06 10:08 ` Elfyn McBratney
2006-09-06 10:18 ` Elfyn McBratney [this message]
2006-09-06 8:14 ` Jakub Moc
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=92c39da00609060318y58af2191tdbca115ed346896@mail.gmail.com \
--to=elfyn.mcbratney@gmail.com \
--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