2012/3/31 Tiziano Müller <dev-z...@gentoo.org>: > Am Samstag, den 31.03.2012, 14:44 +0200 schrieb Ulrich Mueller: >> >>>>> On Sat, 31 Mar 2012, Maciej Grela wrote: >> >> > I've read the PMS and I haven't found information whether this variable >> > is supposed to be set during pkg_prepare or not. >> >> There is no such stage. You mean pkg_pretend, I suppose? >> >> > 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 ? >> >> It's specified here: >> <http://dev.gentoo.org/~ulm/pms/4/pms.html#x1-11900012.1> >> >> | Variable Legal in Consistent? Description >> | --------------------------------------------------------------------- >> | T All Partially⁴ The full path to a temporary >> | directory for use by the ebuild. >> | >> | ⁴Consistent and preserved across a single connected sequence of >> | install or uninstall phases, but not between install and uninstall. >> | When reinstalling a package, this variable must have different >> | values for the install and the replacement. >> >> > Can this be considered as a bug in paludis ? >> >> The spec seems to be clear that T is legal in all phases, including >> pkg_pretend. > > Well, I'd say: there is no sane value you can assign to $T since you are > not allowed to write anything anyway:
indeed it's not writing, check-reqs.eclass is reading space available via 'df -Pm' there is something else it could use assuming $PORTAGE_TMPDIR is worse for portability? > > "pkg_pretend must not write to the > filesystem." (http://dev.gentoo.org/~ulm/pms/4/pms.html#x1-9700010.1.2) > > and since "pkg_pretend is run separately from the main phase function > sequence, and does not participate in any kind of environment saving" it > is not guaranteed to be set to the same $T later. > > Cheers, > Tiziano
