From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: evan.straw99@gmail.com, 45360@debbugs.gnu.org
Subject: bug#45360: Cannot log in to GNOME on foreign distro with Guix
Date: Tue, 22 Dec 2020 14:40:01 +0100 [thread overview]
Message-ID: <87v9cuez7y.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87blemnho1.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 22 Dec 2020 13:34:22 +0100")
Hello,
Ricardo Wurmus <rekado@elephly.net> writes:
> Carlo Zancanaro <carlo@zancanaro.id.au> writes:
>> We should consider this a bug, because Guix's attempt to add to the
>> XDG_DATA_DIRS environment variable clobbers the default value that
>> foreign distributions are relying on.
>
> Is this something we can avoid by patching … something to use a
> Guix-specific variable? This variable can cause a lot of trouble when
> using Guix on foreign distros, but I don’t know how we can prevent
> system software from loading stuff from XDG_DATA_DIRS for Guix and vice
> versa without renaming the variables.
>
> A related question: should Guix software ignore XDG_DATA_DIRS when set
> by the system? Or is it enough to make it respect an *additional*
> variable like GUIX_XDG_DATA_DIRS, which we would have Guix set?
>
>> We should at least document this in the manual, maybe in "(guix)
>> Application Setup".
>
> If it’s an easy workaround: yes. But if it’s a bug we can actually fix
> I’d rather see it fixed :)
I don't think this would be a sufficient workaround anyway. It seems
related to bug 35308 (<http://issues.guix.info/35308>) where
GI_TYPELIB_PATH is also involved.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-12-22 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 5:38 bug#45360: Cannot log in to GNOME on foreign distro with Guix Evan Straw
2020-12-22 11:42 ` Carlo Zancanaro
2020-12-22 12:34 ` Ricardo Wurmus
2020-12-22 13:40 ` Nicolas Goaziou [this message]
2020-12-30 2:29 ` Evan Straw
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=87v9cuez7y.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=45360@debbugs.gnu.org \
--cc=evan.straw99@gmail.com \
--cc=rekado@elephly.net \
/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.