public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Should ${T} be defined in pkg_prepare ?
Date: Sat, 31 Mar 2012 17:36:20 +0200	[thread overview]
Message-ID: <1333208180.4703.11.camel@storm> (raw)
In-Reply-To: <20342.64535.858274.416935@a1i15.kph.uni-mainz.de>

[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]

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:

"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

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3551 bytes --]

  reply	other threads:[~2012-03-31 15:37 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 [this message]
2012-03-31 20:56     ` Ulrich Mueller
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=1333208180.4703.11.camel@storm \
    --to=dev-zero@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