From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Should ${T} be defined in pkg_prepare ?
Date: Sat, 31 Mar 2012 22:56:39 +0200 [thread overview]
Message-ID: <20343.28551.166484.197058@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <1333208180.4703.11.camel@storm>
>>>>> On Sat, 31 Mar 2012, Tiziano Müller wrote:
>> 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:
> "pkg_pretend must not write to the filesystem."
> (http://dev.gentoo.org/~ulm/pms/4/pms.html#x1-9700010.1.2)
That's not necessarily a contradiction. Writing being not allowed
doesn't imply that the directory must not exist.
> 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.
The problem is that apart from T (and maybe HOME), there seems to be
no other directory that check_reqs.eclass could use for its disk space
check in pkg_pretend. WORKDIR doesn't exist in pkg_* phases.
Ulrich
next prev parent reply other threads:[~2012-03-31 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 12:10 [gentoo-dev] Should ${T} be defined in pkg_prepare ? Maciej Grela
2012-03-31 12:44 ` Ulrich Mueller
2012-03-31 15:36 ` Tiziano Müller
2012-03-31 20:56 ` Ulrich Mueller [this message]
2012-03-31 21:24 ` Zac Medico
2012-04-01 8:29 ` Ulrich Mueller
2012-04-01 18:49 ` Zac Medico
2012-03-31 21:01 ` Francesco Riosa
2012-04-01 18:55 ` Ciaran McCreesh
2012-04-01 20:13 ` Maciej Grela
2012-04-01 20:47 ` Michał Górny
2012-04-01 21:00 ` Ciaran McCreesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20343.28551.166484.197058@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox