public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Nilsson <john@milsson.nu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Extra USE field
Date: Mon, 26 Jul 2004 01:23:37 +0200	[thread overview]
Message-ID: <1090797817.4325.14.camel@newkid.milsson.nu> (raw)
In-Reply-To: <33525.68.78.46.139.1090796608.squirrel@68.78.46.139>

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

On Mon, 2004-07-26 at 01:03, Joseph Booker wrote:
> On Sun, July 25, 2004 5:58 pm, John Nilsson said:
> > Why not drop global useflags entierly?
> >
> > There really is no reason for them. Extend euse to modify
> > /etc/portage/packages.use.
> >
> > I think it is time to begin decentralizing the system now. Portage is
> > getting rather large and will probably be broken up into pieces in the
> > future. If ebuilds didn't have to concider some global useflag namespace
> > it would be eaiser to sync diffrent vendors trees.
> >
> > -John
> >
> 
> 
> :( so instead of adding USE="gnome" to make.conf, i would have to check
> every package i emerge to see if it uses the 'gnome',
> 'gnomelib','gnome-integratoin', or w/e other local use flag (since the
> names wouldn't be standardized) and add those to /etc/portage/package.use?
> that one file could get *really* big, I use *alot* of USE flags

I'm thinking a more automatic aproach... like:

howabout dropping /etc/portage/package.use and just utilize the
/var/db/pkg files?

USE="useflag" emerge package

USE will cascade over the /var/db/pkg/cat/package/USE

-John

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-07-25 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25 19:52 [gentoo-portage-dev] Extra USE field Joel Konkle-Parker
2004-07-25 21:33 ` Douglas Russell
2004-07-25 22:58 ` John Nilsson
2004-07-25 23:03   ` Joseph Booker
2004-07-25 23:23     ` John Nilsson [this message]

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=1090797817.4325.14.camel@newkid.milsson.nu \
    --to=john@milsson.nu \
    --cc=gentoo-portage-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