On 1/21/2013 12:38, Rick "Zero_Chaos" Farina wrote:
On 01/21/2013 01:15 PM, Dustin C. Hatch wrote:
I am curious what the correct way to set Portage/make.conf
variables, besides USE, for building stages is. In particular, I'd
like to know how to set FEATURES, MAKEOPTS, and
EMERGE_DEFAULT_OPTS. I've tried setting them in
/etc/catalyst/catalystrc, but that has the nasty side effect of
negating entries in portage_confdir/env. Is there a better way to
set these?
like this:
export EMERGE_DEFAULT_OPTS="$(portageq envvar EMERGE_DEFAULT_OPTS) --jobs"
you call in the current values and append.
- -Zero
Okay, but that still doesn't solve the problem of environment variables
overriding the per-package settings in /etc/portage/env. I need this
because there are a couple of packages that refuse to build with
MAKEOPTS other than -j1 or if FEATURES includes distcc. I don't want to
have to disable those things to build the whole system, just those
couple of packages.
--
♫Dustin
