| 1 |
On Mon, 2001-11-26 at 09:42, Sean Mitchell wrote: |
| 2 |
> |
| 3 |
> > Some people have suggested that they would like to be |
| 4 |
> > able to set some |
| 5 |
> > USE variables for specific apps.....examples escape me, but I |
| 6 |
> > know it has |
| 7 |
> > been brought up. |
| 8 |
> |
| 9 |
> I don't like the idea of making app-specific settings in a global file. |
| 10 |
|
| 11 |
Agreed. |
| 12 |
|
| 13 |
> For my money I think that a command line switch to emerge/ebuild to |
| 14 |
> turn certain USE variables on or off would be better. The idea that |
| 15 |
> a user ALWAYS or NEVER wants to use a particular thing seems a bit |
| 16 |
> rigid to me. |
| 17 |
|
| 18 |
You can do this with BASH already. just set the use variably as you |
| 19 |
like it and then emerge. or |
| 20 |
|
| 21 |
% USE="foo bar baz" emerge foo/bar |
| 22 |
|
| 23 |
I am not up on the syntax, but you can also use += or -= to remove |
| 24 |
variables, I think. |
| 25 |
|
| 26 |
Chad |
Archives