Summary: | app-office/libreoffice-3.3.2 build env pollution | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Laurent G. <lauranger> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build full log |
Description
Laurent G.
2011-05-01 17:52:07 UTC
1) Please attach the entire build log. 2) Attach the environment file the package uses. Created attachment 272037 [details]
build full log
Hi
What is the environment file ?
Do I have to start the ebuild again ?
Thanks in advance.
Laurent G.
AFAIK it should be impossible for any ebuild/eclass run by emerge to leak environment variables back to the shell where emerge was started. And how permanent are these leaked variables anyway? Does TMPDIR show up in other freshly launched shells? (In reply to comment #3) > AFAIK it should be impossible for any ebuild/eclass run by emerge to leak > environment variables back to the shell where emerge was started. > > And how permanent are these leaked variables anyway? Does TMPDIR show up in > other freshly launched shells? The leak was only in the shell that launched the emerge. I opened a new terminal tab in konsole and the bash in it had no TMPDIR. (In reply to comment #2) > What is the environment file ? That would be in the package's build directory, so something like: /var/tmp/portage/app-office/libreoffice/temp/environment > Do I have to start the ebuild again ? Yes. |