all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Tk <tk.code@protonmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Package recommended environment variables
Date: Thu, 16 May 2019 13:21:12 +0200	[thread overview]
Message-ID: <87tvduhcgn.fsf@nckx> (raw)
In-Reply-To: <fta23p8VGQm4AeatcWGb6ifmNhNLGkg7zfs-Fs3SYpEDqq2_8lZ1BT-sWrxBwd6STvvFd5YDk6TU8sp0aTdxarJGM8k5nq2nkk-0v9jTorQ=@protonmail.com>

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

Tk,

Tk wrote:
> When installing packages, I often get warnings about adding 
> variables to .profile .

Which warnings are these?  Are you sure that's what they mean?

Something like ‘the following variable definitions might be 
needed’ doesn't mean you should go edit your .profile, but you're 
far from the first to do so.  They are printed because guix cannot 
change the environment of the shell that invoked it, so ‘guix 
install foo; foo’ won't work if foo needs a certain environment 
variable to be set.  It will work if you open a new shell.  That's 
a Unix limitation¹.

There was some talk about rephrasing that warning, but IIRC that 
was difficult to do without making other assumptions.  I don't 
know if anything came of it.

> These warnings, however, get easily lost when installing bunch 
> of stuff automatically. Is there a way of extracting this info 
> again? Should I grep through package definitions?

Grepping won't help since these variables (‘search paths’) are 
almost always propagated from dependencies, such as glib.  Take a 
look at the ‘--search-paths’ argument to ‘guix package’.  It will 
probably do what you want.  Note that it's not limited to a single 
package.

However, why are you interested in this information?

- If it's because you're manually adding variables to .profile: 
  don't; Guix already takes care of this automatically, you should 
  simply source <guix-profile>/etc/profile if you aren't already.

- If it's because you're using an incompatible shell and are 
  maintaining your own ‘port’ of that file: you're *probably* 
  better off with a simple ‘bash -c ". guix-profile/etc/profile && 
  exec myshell"’ wrapper.

- If it's because Guix's …/etc/profile is otherwise lacking for 
  you, please let us know why.

Kind regards,

T G-R

[1]: There are horrible ways to fake this but let's not.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2019-05-16 11:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  9:25 Package recommended environment variables Tk
2019-05-16 11:11 ` Amirouche
2019-05-18  3:41   ` Ricardo Wurmus
2019-05-16 11:21 ` Tobias Geerinckx-Rice [this message]
2019-05-16 13:13   ` Tk
2019-05-18  3:40     ` Ricardo Wurmus
2019-05-16 13:27   ` Jeff Bauer
2019-05-18  0:52 ` ison

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=87tvduhcgn.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=tk.code@protonmail.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.