all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 53447@debbugs.gnu.org, Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#53447] Introducing ‘GUIX_’-prefixed environment variables
Date: Tue, 25 Jan 2022 14:29:41 +0100	[thread overview]
Message-ID: <87lez4lz96.fsf_-_@gnu.org> (raw)
In-Reply-To: <87y2344vnv.fsf_-_@gmail.com> (Maxim Cournoyer's message of "Mon,  24 Jan 2022 17:27:00 -0500")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> I like to see this as a bug, so I've opened one as 53514; Guix should
> strive to not mess with the host environment, and setting global
> variables used by both Guix and a potentially foreign host goes against
> this.  The proper fix would be to patch all applications in Guix to use
> Guix-specific variables, such as GUIX_XDG_DATA_DIRS instead of
> XDG_DATA_DIRS.

This approach has its appeal (like in the ‘GUIX_PYTHONPATH’ case), but
there’s a tension with our other unwritten (?) guideline that we should
modify packages as little as possible.

Such wide-ranging changes would have the unfortunate effect that they’d
make Guix packages “special”: documentation, bug reports, suggestions
you’d find online would apply to the “real” package, but maybe not to
the Guix one.  That is a situation we’d rather avoid IMO.


‘XDG_DATA_DIRS’ is a real problem though.  In large part that’s because
its purpose is too broad—what “data dirs” are we talking about?  It
would be ideal if we could progressively replace ‘XDG_DATA_DIRS’ search
path specifications with more specific environment variables, when they
exist, or perhaps by using ‘wrap-program’ instead of having search path
specs.

Right now there are 9 packages that have ‘XDG_DATA_DIRS’ as their search
path, including 4 Common Lisp packages.  Of the remaining ones, I guess
those we should first focus on are glib and qtbase.

Thoughts?

Ludo’.




  reply	other threads:[~2022-01-25 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22 14:13 [bug#53447] [PATCH] doc: Unset environment variables considered harmful Liliana Marie Prikler
2022-01-22 16:04 ` Ludovic Courtès
2022-01-22 17:53   ` Liliana Marie Prikler
2022-01-24 22:27     ` Maxim Cournoyer
2022-01-25 13:29       ` Ludovic Courtès [this message]
2022-01-26  1:56         ` [bug#53447] Introducing ‘GUIX_’-prefixed environment variables Maxim Cournoyer
2022-01-26 12:05           ` Ludovic Courtès
2022-01-26 20:03             ` Liliana Marie Prikler
2022-01-27  4:53               ` Maxim Cournoyer
2022-01-25  7:39     ` [bug#53447] [PATCH] doc: Unset environment variables considered harmful Ludovic Courtès
2022-01-25 19:21       ` Liliana Marie Prikler

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=87lez4lz96.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=53447@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=maxim.cournoyer@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.