From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Dealing with XDG directories in ebuild environment
Date: Sat, 25 Jan 2014 22:00:06 +0100 [thread overview]
Message-ID: <1390683606.24148.271.camel@belkin5> (raw)
In-Reply-To: <CAJ0EP42143-BM5sQHbjP4ua-F-GMzQKk-23_BGMb=EjCDK59iw@mail.gmail.com>
El sáb, 25-01-2014 a las 11:13 -0500, Mike Gilbert escribió:
> It seems having XDG variables like XDG_CONFIG_HOME set in the
> environment when calling emerge has a tendency to cause sandbox
> violations. For example, see the bugs blocking bug 499202.
>
> https://bugs.gentoo.org/show_bug.cgi?id=499202
>
> If you grep for XDG_CONFIG_HOME in the eclass directory, you can see
> that several eclasses work around this by setting
> XDG_CONFIG_HOME="${T}" or "${T}/.config".
>
> gnome2-utils.eclass takes it a step further and creates empty
> directories for several other XDG variables.
>
> Is this something we can/should consolidate into some central place?
> Or should I just copy/paste something into distutils-r1.eclass?
>
Maybe the function cleaning stuff could be added to eutils.eclass and we
would call it from other eclasses/ebuilds. I also wonder if this cleanup
could be done always in a newer eapi since we usually need to add that
fix whenever we suffer the sandbox violation :S (not before)
next prev parent reply other threads:[~2014-01-25 21:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 16:13 [gentoo-dev] Dealing with XDG directories in ebuild environment Mike Gilbert
2014-01-25 21:00 ` Pacho Ramos [this message]
2014-01-25 21:16 ` Michał Górny
2014-01-26 0:10 ` Mike Gilbert
2014-01-26 0:19 ` Mike Gilbert
2014-01-26 20:43 ` Alec Warner
2014-01-26 20:49 ` Ciaran McCreesh
2014-01-26 21:21 ` Alec Warner
2014-01-26 21:35 ` Ciaran McCreesh
2014-01-26 21:59 ` Michał Górny
2014-01-26 22:03 ` Ciaran McCreesh
2014-01-26 23:05 ` Mike Gilbert
2014-01-27 1:10 ` Peter Stuge
2014-01-27 23:02 ` Gilles Dartiguelongue
2014-01-28 17:03 ` Mike Gilbert
2014-01-29 5:44 ` Alexandre Rostovtsev
2014-01-29 6:37 ` Alexandre Rostovtsev
2014-01-29 16:46 ` Mike Gilbert
2014-01-29 8:58 ` Jan Matejka
2014-01-29 16:13 ` Alexandre Rostovtsev
2014-01-28 13:11 ` [gentoo-dev] " Steven J. Long
2014-01-29 22:53 ` Gilles Dartiguelongue
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=1390683606.24148.271.camel@belkin5 \
--to=pacho@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