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