| 1 |
On 03/18/2012 12:18 AM, Duncan wrote: |
| 2 |
> What's you're definition of "sane"? Does it include the |
| 3 |
> /etc/portage/package.env and/or /etc/portage/env/cat-egory/pkg files |
| 4 |
> configuration options? |
| 5 |
> |
| 6 |
> I've been using (and prefer) the latter for quite some time for various |
| 7 |
> per-package settings (tho not the particular one in question here) |
| 8 |
> without an issue. The former is newer but somewhat more limited, to |
| 9 |
> make.conf style direct variable assignments, while the latter allows full |
| 10 |
> bash flexibility, which I take advantage of. |
| 11 |
|
| 12 |
For best results, you should use package.env for FEATURES settings, |
| 13 |
because it's applied very early, so it will even take care of enabling |
| 14 |
USE=test when resolving dependencies. On the other hand, bashrc settings |
| 15 |
are applied much later, when the ebuild is being executed by bash. As a |
| 16 |
general rule of thumb, use package.env for anything that involves |
| 17 |
variable settings alone, and use bashrc for anything that must be |
| 18 |
executed by bash. |
| 19 |
-- |
| 20 |
Thanks, |
| 21 |
Zac |
Archives