| 1 |
On Wednesday 10 November 2004 13:21, Brian Harring wrote: |
| 2 |
> On Wed, 2004-11-10 at 01:36, Paul de Vrieze wrote: |
| 3 |
> > On Tuesday 09 November 2004 16:26, Aron Griffis wrote: |
| 4 |
> > > Aaron Walker wrote: [Tue Nov 09 2004, 05:26:28AM EST] |
| 5 |
> > > |
| 6 |
> > > > Comments/suggestions/flames? |
| 7 |
> > > |
| 8 |
> > > It's a lot easier to override make.conf via environment variables. |
| 9 |
> > > All the variables either directly override or augment when they're |
| 10 |
> > > in the environment. |
| 11 |
> > |
| 12 |
> > Alternatively you could use /etc/portage/bashrc |
| 13 |
> |
| 14 |
> That's not going to fly for most feature tweaks, added, make.conf |
| 15 |
> defines a fair amount of python specific vars that bashrc knows nothing |
| 16 |
> off. Fex, doesn't do you a lot of good to be tweaking |
| 17 |
> FEATURES="userpriv" in bashrc- the bash process is already running as |
| 18 |
> root at that point. |
| 19 |
|
| 20 |
I don't see why you would want to change this kind of variables based on a |
| 21 |
runlevel. In such cases I think an emerge wrapper is probably most |
| 22 |
suited. |
| 23 |
|
| 24 |
Paul |
| 25 |
|
| 26 |
-- |
| 27 |
Paul de Vrieze |
| 28 |
Gentoo Developer |
| 29 |
Mail: pauldv@g.o |
| 30 |
Homepage: http://www.devrieze.net |
Archives