On Tue, Apr 19, 2005 at 06:07:36PM +0100, Ciaran McCreesh wrote:
> On Tue, 19 Apr 2005 17:48:55 +0100 Digby Tarvin <[EMAIL PROTECTED]> wrote:
> | An 'export HISTFILE=""' seemed to work around it, but I am not sure if
> | this should be reported as an 'emerge' bug or a 'mozilla' package bug.
> | 
> | Is there any reason why I should not run emerge after logging in as
> | myself and then 'su'ing? Are there guidelines on acceptable
> | environment settings that should be present when doing an emerge which
> | I have overlooked?
> 
> Hrm, I'd say that this isn't a bug, personally. Although it is another
> good example of why we need that restricted environment stuff that our
> portage people (I think it was Brian?) were thinking about...

well - if it stopped it working I wouldn't call it a feature ;)

I quite agree about the restricted environment. On other systems where I
manage open source software installation manually, I always create
a diretory in /usr/local/src for the tarball, and then su to a dedicated
user (local) to build and install. Only the occasional priveledged
application (like sudo) needs to be installed as root, and for that
I do a 'make -n install' and execute the commands manually.

Perhaps part of the emerge restricted environment should involve
clearing the environment settings of everything that isn't
explicitly recognized. It would probably place a bit much of a
burden on package builders to expect them to be able to deal
with arbitrary environment settings.

Quite appart from security issues, it certainly seems important that
an operation which rebuilds a significant portion of the system should
have reproducible results that don't depend on the details of the personal
environment of the person that runs it.

I suppose at least if an environment variable is going to have an
unexpected side effect on an 'update world', having the build fail
is preferable to silently producing an flawed system.

Regards,
DigbyT
-- 
Digby R. S. Tarvin                                             [EMAIL PROTECTED]
http://www.digbyt.com
-- 
[email protected] mailing list

Reply via email to