unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Ethan Blanton <elb@kb8ojh.net>, 56076@debbugs.gnu.org
Subject: bug#56076: guix shell -P behavior is surprising with persistent home
Date: Tue, 28 Jun 2022 09:43:46 +0200	[thread overview]
Message-ID: <87bkudfd1p.fsf@gnu.org> (raw)
In-Reply-To: <16baeb96695dcceefca352ff9660ca6d2b87754b.camel@telenet.be> (Maxime Devos's message of "Mon, 27 Jun 2022 10:37:21 +0200")

Hi,

Maxime Devos <maximedevos@telenet.be> skribis:

>> > Having to add openssl looks like a bug,
>> 
>> It is, but it’s a reasonable solution for the problem at hand.
>
> I don't think it is.

On another distro, you might have to set SSL_CERT_DIR manually.  It’s
not that big of a deal, or at least not really worse.

[...]

> My patch <https://issues.guix.gnu.org/55297> could be considered a
> work-around, but at least it's automatic for the users, users don't
> need to remember random Guix bug facts.

If we start adding such workarounds, where do we stop?  Someone will
want to have similar workarounds for TERMINFO_DIRS; do we add that to
each and every package that uses ncurses?  What about GST_PLUGIN_PATH?

So far, we’ve addressed those by special-casing a few key variables in
/etc/profile on Guix System and similarly in the file generated by the
install script on foreign distros.

Maybe we could do the same with SSL_CERT_DIR?

> Ludovic Courtès schreef op ma 27-06-2022 om 09:55 [+0200]:
>> That’s a bit of a hack to work around this venerable bug:
>> 
>>   https://issues.guix.gnu.org/22138
>> 
>> :-)
>
> Maybe yes, but there's no progress there

True, but that doesn’t mean it has to stay that way.

I understand your frustration (I really do!) and I agree that sometimes
we need workarounds when there’s no “proper” solution in sight.  Our
disagreement is about the kind of workaround in this case; I’m reluctant
to adding search path definitions to users of a library that defines it.

Thanks,
Ludo’.




  reply	other threads:[~2022-06-28  8:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18 21:41 bug#56076: guix shell -P behavior is surprising with persistent home Ethan Blanton via Bug reports for GNU Guix
2022-06-24 21:10 ` Ludovic Courtès
2022-06-24 21:18   ` Maxime Devos
2022-06-27  7:55     ` Ludovic Courtès
2022-06-27  8:37       ` Maxime Devos
2022-06-28  7:43         ` Ludovic Courtès [this message]
2022-06-28 10:50           ` Maxime Devos
2022-06-28 12:08           ` Maxime Devos

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bkudfd1p.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=56076@debbugs.gnu.org \
    --cc=elb@kb8ojh.net \
    --cc=maximedevos@telenet.be \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).