unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
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 12:50:06 +0200	[thread overview]
Message-ID: <da2ccfa7eccd1bf4eb7f6c82f631bcf34dfe3f37.camel@telenet.be> (raw)
In-Reply-To: <87bkudfd1p.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]

> 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.

On other distros, that's sufficient because they only have global
installation, in /etc/ssl/certs. So I don't think it's a good
comparison, given that Guix is all about user-level and occassionally
ad-hoc "guix shell".

Ludovic Courtès schreef op di 28-06-2022 om 09:43 [+0200]:
> > 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?

Sounds good.

> So far, we’ve addressed those by special-casing

That seems equally workaround to me?  Though way less work so sounds
good, except for it being rejected in the past.

> 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?

Shouldn't this be $GUIX_ENVIRONMENT/etc/profile instead of
/etc/profile?  Otherwise, it wouldn't have any effect on "guix shell".
Also, I believe I have proposed making some other variables behave like
$PATH as well, but you rejected it for being special-cased and magic.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-06-28 10:51 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
2022-06-28 10:50           ` Maxime Devos [this message]
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=da2ccfa7eccd1bf4eb7f6c82f631bcf34dfe3f37.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56076@debbugs.gnu.org \
    --cc=elb@kb8ojh.net \
    --cc=ludo@gnu.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.
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).