From: Gilles Dartiguelongue <eva@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, freedesktop-bugs@gentoo.org
Subject: Re: [gentoo-dev] Re: New eclass: xdg-basedir
Date: Thu, 30 Jan 2014 09:35:04 +0100 [thread overview]
Message-ID: <1391070904.6850.2.camel@kanae> (raw)
In-Reply-To: <21226.3444.956884.122969@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Le jeudi 30 janvier 2014 à 09:29 +0100, Ulrich Mueller a écrit :
> >>>>> On Thu, 30 Jan 2014, Gilles Dartiguelongue wrote:
>
> > The thing with ${HOME} is that it should not be a directory where
> > XDG compliants tools should be able to store anything permanent
> > while building since this would affect consecutive builds (say
> > gobject-introspection, gstreamer registry, etc).
>
> > This is why it is set to ${T} in gnome2-utils.eclass.
>
> HOME is as temporary as T during build time. PMS says: "The full path
> to an appropriate temporary directory for use by any programs invoked
> by the ebuild that may read or modify the home directory."
>
> With Portage, HOME will point to:
> ${PORTAGE_TMPDIR}/${CATEGORY}/${PF}/homedir/
>
Very well then.
--
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-30 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 3:37 [gentoo-dev] New eclass: xdg-basedir Mike Gilbert
2014-01-30 8:11 ` [gentoo-dev] " Gilles Dartiguelongue
2014-01-30 8:24 ` Jonathan Callen
2014-01-30 8:29 ` Ulrich Mueller
2014-01-30 8:35 ` Gilles Dartiguelongue [this message]
2014-01-30 11:48 ` Michael Palimaka
2014-01-30 13:03 ` Ulrich Mueller
2014-01-30 14:45 ` Jeroen Roovers
2014-01-30 15:44 ` [gentoo-dev] Shell function names (was: New eclass: xdg-basedir) Ulrich Mueller
2014-01-30 17:32 ` [gentoo-dev] Re: New eclass: xdg-basedir Mike Gilbert
2014-01-30 17:45 ` Michael Palimaka
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=1391070904.6850.2.camel@kanae \
--to=eva@gentoo.org \
--cc=freedesktop-bugs@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@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