From: Rick van Hattem <Rick.van.Hattem@fawo.nl>
To: gentoo-user@lists.gentoo.org
Cc: "Vlad Dogaru" <ddvlad@gmail.com>
Subject: Re: [gentoo-user] USE Flags
Date: Sun, 10 Dec 2006 18:34:05 +0100 [thread overview]
Message-ID: <200612101834.05589.Rick.van.Hattem@fawo.nl> (raw)
In-Reply-To: <bf0e048a0612100818q2cc47a75j85b38a5869fe76b0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Sunday 10 December 2006 17:18, Vlad Dogaru wrote:
> On 12/10/06, Neil Bothwick <neil@digimed.co.uk> wrote:
> > On Sun, 10 Dec 2006 11:35:18 +0200, Vlad Dogaru wrote:
> > > If it is, is there a way of dumping
> > > all the use flags for all my currently installed ebuilds into
> > > packages.conf?
> >
> > You really don't want to do that. you'd end up with an unmanageable mess
> > that completely overrides /etc/make.conf and your profile.
> >
> > If you run "emerge -puvDN world" you'll see all packages that are
> > installed with different USE flags to the current settings. Add these
> > to /etc/portage/package.use.
>
> I think this is exactly what I was looking for. I already have quite an
> extensive global USE list (read through the whole list and set/unset what I
> knew about). I only need to write the different, package-specific ones.
>
> Thanks to everyone for enlightening me on the issue,
> Vlad
To manage the global use flags, try profuse, it's a pretty good editor imho.
--
Rick van Hattem Rick.van.Hattem(at)Fawo.nl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-10 17:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 9:35 [gentoo-user] USE Flags Vlad Dogaru
2006-12-10 9:46 ` Raymond Lewis Rebbeck
2006-12-10 9:55 ` Uwe Thiem
2006-12-10 11:20 ` Neil Bothwick
2006-12-10 16:18 ` Vlad Dogaru
2006-12-10 17:34 ` Rick van Hattem [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-25 16:55 [gentoo-user] Use Flags Silvio Siefke
2012-07-25 17:07 ` Yohan Pereira
2012-07-26 6:42 ` Alan McKinnon
2012-07-26 13:22 ` Allan Gottlieb
2012-07-26 18:53 ` Alan McKinnon
2006-04-05 14:28 [gentoo-user] USE flags Leonid Podolny
2006-03-09 11:19 Goran Maksimoviæ
2006-03-09 16:29 ` Daniel da Veiga
2006-03-09 17:15 ` Richard Fish
2006-03-09 18:22 ` Goran Maksimović
2006-03-10 1:52 ` Boyd Stephen Smith Jr.
2005-12-02 20:14 Jeff
2005-12-02 20:58 ` Neil Bothwick
2005-12-02 21:02 ` Dale
2005-12-02 22:20 ` John J. Foster
2005-10-24 22:13 Eric Waguespack
2005-10-24 22:19 ` Hemmann, Volker Armin
2005-10-24 22:21 ` Dave Nebinger
2005-10-24 22:21 ` Holly Bostick
2005-10-24 22:22 ` Petteri Räty
2005-10-24 22:24 ` Brett I. Holcomb
2005-10-25 15:24 ` Neil Bothwick
2005-10-25 19:55 ` Mark Shields
2005-10-25 23:58 ` Neil Bothwick
2005-10-24 22:29 ` Willie Wong
2005-10-24 23:11 ` Holly Bostick
2005-08-20 0:46 John Dangler
2005-08-20 1:50 ` Marco Matthies
2005-08-20 2:19 ` John Dangler
2005-08-20 2:26 ` John Jolet
2005-08-20 2:37 ` Marco Matthies
2005-08-20 3:53 ` Walter Dnes
2005-08-20 13:48 ` Peter O'Connor
2005-07-18 16:58 Vincent A. Primavera
2005-07-18 17:24 ` Vincent A. Primavera
2005-07-18 15:24 Vincent A. Primavera
2005-07-18 15:38 ` Dave Nebinger
2005-07-18 15:53 ` Rumen Yotov
2005-07-18 17:17 ` Marco Matthies
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=200612101834.05589.Rick.van.Hattem@fawo.nl \
--to=rick.van.hattem@fawo.nl \
--cc=ddvlad@gmail.com \
--cc=gentoo-user@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