r app-office/libreoffice:0::gentoo 3.5.2.2 to ::installed replacing
3.5.2.2
(-aqua) -binfilter branding cups dbus eds gnome graphite gstreamer
gtk -java jemalloc -kde -mysql -nlpsolver nsplugin -odk opengl pdfimport
-postgres svg vba webdav xmlsec (-test) build_options: symbols=split
-optional_tests -trace -preserve_work
Reasons: target, !=app-office/libreoffice-3.4.9999-r1 from
app-office/libreoffice-l10n, !=app-office/libreoffice-9999-r1 from
app-office/libreoffice-l10n, 2 more
Total: 1 reinstalls
Executing pretend actions: 1 of 1
libreoffice-3.5.2.2> * Checking for at least 512 mebibytes RAM ...
[ ok ]
libreoffice-3.5.2.2> DISK CHECK: path="", size="6G"
libreoffice-3.5.2.2> * Checking for at least 6 gibibytes disk space at
[ !! ]
libreoffice-3.5.2.2>
libreoffice-3.5.2.2> * Couldn't determine disk space, skipping...
8< -------------------------------------------------
the check-reqs is not getting the "${T}" value properly when it's being
run from pkg_prepare. I've added an echo to the eclass to confirm this.
The ebuild detects free space properly when run under emerge:
Total: 1 package (1 reinstall), Size of downloads: 0 kB
>>> Verifying ebuild manifests
>>> Running pre-merge checks for app-office/libreoffice-3.5.2.2
* Checking for at least 512 mebibytes RAM
...
[ ok ]
DISK CHECK: path="/var/tmp/portage/app-office/libreoffice-3.5.2.2/temp",
size="6G"
* Checking for at least 6 gibibytes disk space at
"/var/tmp/portage/app-office/libreoffice-3.5.2.2/temp"
... [ ok ]
>>> Emerging (1 of 1) app-office/libreoffice-3.5.2.2
^C
I've read the PMS and I haven't found information whether this variable
is supposed to be set during pkg_prepare or not. Therefore I ask, what
is the proper behaviour here ? Is there documentation on what special
env variables are supposed to be defined in each stage ?
Can this be considered as a bug in paludis ?