public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Pacho Ramos <pacho@gentoo.org>, gentoo-dev@lists.gentoo.org
Cc: Mart Raudsepp <leio@gentoo.org>, Mike Gilbert <floppym@gentoo.org>
Subject: [gentoo-dev] Re: profiles/base/make.defaults: add XDG_DATA_DIRS & XDG_CONFIG_DIRS to ENV_UNSET
Date: Tue, 6 Aug 2024 13:27:21 -0400	[thread overview]
Message-ID: <CAJ0EP42bm8MYLNaKkhN36M3YiDPfq-LE+mj2=-bcA9bt2dxXtg@mail.gmail.com> (raw)
In-Reply-To: <74b03b9eb4be6825a1c21d3fe828b3cf16843ff3.camel@gentoo.org>

On Wed, Jul 17, 2024 at 2:57 PM Pacho Ramos <pacho@gentoo.org> wrote:
>
> Hello,
>
> This is a follow up from an older thread by leio in the mailing list:
> https://archives.gentoo.org/gentoo-dev/message/bf36c4c50f9c15db222faa6a66b0c6c9
>
> The problem is that, at present time, we are getting more and more bugs
> coming from flatpak users that get build failures due to having those
> variables "polluted".
>
> Personally, I would opt for unsetting them too and properly set them to
> known values for packages needing it. But I am unsure if we could
> probably do a tinderbox run to find&fix packages needing them to be set
> :-/

I'm not really familiar with the packages that require these
variables. I agree with the idea in principle though.

It seems like x11-libs/gtk+ is one example given by leio. How would we
fix that one? Can the same strategy be applied to similar ebuilds?

Another possible idea would be to source /etc/profile.env in a
subshell and pick out the relevant XDG variables in
xdg_environment_reset.


      reply	other threads:[~2024-08-06 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 18:57 [gentoo-dev] profiles/base/make.defaults: add XDG_DATA_DIRS & XDG_CONFIG_DIRS to ENV_UNSET Pacho Ramos
2024-08-06 17:27 ` Mike Gilbert [this message]

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='CAJ0EP42bm8MYLNaKkhN36M3YiDPfq-LE+mj2=-bcA9bt2dxXtg@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=leio@gentoo.org \
    --cc=pacho@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