Re: [gentoo-soc] Auto dependency builder progress report. Week 5.

[Fabian Groffen <grobian@gentoo.org>]

On 29-06-2011 13:28:45 +0600, Александр Берсенев wrote:
> Then I began to log all environment variables and find then someone
> changes my LOG_SOCKET variable during "prerm" stage. I renamed it to
> LOG_SOCKET_<LONG_STRING> in all sources hoping this is a
> name-collision. But variable continues changing its value. The most
> interesting fact: value was changing to another valid socket name, for
> example from "/tmp/tmpFSDhf/socket_for_logging" to
> "/tmp/tmpHDvJ5/socket_for_logging". But nobody listened
> "/tmp/tmpHDvJ5/socket_for_logging". I started to believe in the higher
> powers in this moment because last socket file was created five days
> ago and notebook has been rebooted several times these days.
> 
> But the explanation was simple: portage system remembers all
> environment variables while installing a package and restores them
> while removing this package!!

You can add your variable(s) to a white/blacklist in the code that saves
the environment.
Check save_ebuild_env() in isolated-functions.sh.


-- 
Fabian Groffen
Gentoo on a different level