Gentoo Archives: gentoo-user

From: Michael Mol <mikemol@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: How to easily find out what USE flags are redundant in make.conf and package.use?
Date: Sun, 02 Oct 2011 14:54:57
Message-Id: CA+czFiAQWNFrsJKx8K8Q2qJpL4TzD-+Ubbfcmq=i=_+bjBQmiA@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: How to easily find out what USE flags are redundant in make.conf and package.use? by Alan McKinnon
1 On Sun, Oct 2, 2011 at 7:58 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote:
2 > On Sun, 02 Oct 2011 06:36:54 -0500
3 > Dale <rdalek1967@×××××.com> wrote:
4 >> Alan McKinnon wrote:
5 >> > On Sun, 02 Oct 2011 05:13:49 -0500
6 >> > Dale<rdalek1967@×××××.com>  wrote:
7 > You often mention the attraction of Gentoo is you get only what you
8 > want. But, consider this; if you put flags routinely in make.conf you
9 > lose most of that benefit. You end up with the equivalent of Mandrake
10 > where you complied it yourself, not the binary distro.
11 >
12 > USE="<every possible flag enabled>" emerge something and
13 > yum install something and pretty much equivalent in terms of end
14 > result.
15
16 I'm actually very much in Dale's usage pattern here. If there's a
17 feature I want, and it's a globally-valid USE flag (such as, say,
18 ipv6), I put it in make.conf. If there's a feature I want, and it's
19 package-specific, it goes in package.use. If there's a feature I want,
20 it's a globally-valid USE flag, but I *don't* want it in a particular
21 package (say, X in vim), the enabler goes in make.conf, the disabler
22 goes in packages.use; for 90% of packages, I want that support.
23
24 So that's not USE=<every possible flag enable>, that's USE=<all the
25 global flags I want enabled>.
26
27 --
28 :wq

Replies