| 1 |
On Fri, 18 Mar 2016 10:09:14 +0000, Peter Humphrey wrote: |
| 2 |
|
| 3 |
> > You will develop your way of doing things over time, and that way |
| 4 |
> > could change as your needs do. Using your example of package.use, |
| 5 |
> > moving USE flags from package.use to make.conf is an easy enough task |
| 6 |
> > if you need to change. I tend to put them n package.use to start with |
| 7 |
> > then migrate to make.conf if I find I am using the same flag on |
| 8 |
> > several packages. |
| 9 |
> |
| 10 |
> A simple way to start off is to see whether the USE flag is listed in |
| 11 |
> /usr/portage/profiles/use.desc or use.local.desc. If the former, it's |
| 12 |
> likely to affect many packages in a typical system so put it in |
| 13 |
> make.conf; if the latter, it's likely to affect only a few of your |
| 14 |
> packages so put it in package.use. You can always move it later if you |
| 15 |
> want to, as Neil says. |
| 16 |
|
| 17 |
|
| 18 |
app-portage/euses is an easy way of looking up USE flags, give it the |
| 19 |
name of a flag and it shows you the description. If it shows one or more |
| 20 |
package names, the USE flag is defined in local.desc. |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Neil Bothwick |
| 25 |
|
| 26 |
Top Oxymorons Number 33: American history |
Archives