From: "Ludovic Courtès" <ludo@gnu.org>
To: 46803@debbugs.gnu.org
Cc: luis.felipe.la@protonmail.com
Subject: bug#46803: User manual does not explain Profiles (nor GUIX_PROFILE)
Date: Mon, 01 Mar 2021 10:59:35 +0100 [thread overview]
Message-ID: <87tupvtcs8.fsf@gnu.org> (raw)
In-Reply-To: <877dmube5x.fsf@nckx> (Tobias Geerinckx-Rice via Bug reports for's message of "Sat, 27 Feb 2021 00:30:18 +0100")
Hi,
Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
skribis:
> I think that would be very helpful. I'm trying to think of a concise,
> correct, but actually useful definition of profiles for someone not
> already familiar with them or Guix.
>
> Out of curiosity: how do you intuitively understand profiles, as
> someone who's used Guix for a while?
I’m not Luis but I usually say that a profile is the location of a set
of installed packages.
> Luis Felipe via Bug reports for GNU Guix 写道:
>> [...] what is the GUIX_PROFILE variable, does it accept a single
>> path to a profile or more, and some use cases and examples. [...]
>
> I don't think we should document GUIX_PROFILE. It's not part of the
> definition of Guix profiles. It should not matter to users nor should
> they rely on previously observed behaviour. AIUI there are no
> supported ‘use cases’, beyond copy-pasting Guix error messages...
Agreed. ‘GUIX_PROFILE’ has no significance as an environment variable;
it’s referred to by the generated ‘etc/profile’, but it’s usually a
shell variable, not an environment variable.
Ludo’.
next prev parent reply other threads:[~2021-03-01 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 21:24 bug#46803: User manual does not explain Profiles (nor GUIX_PROFILE) Luis Felipe via Bug reports for GNU Guix
2021-02-26 23:30 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-02-27 18:11 ` Luis Felipe via Bug reports for GNU Guix
2021-03-01 9:59 ` Ludovic Courtès [this message]
2021-03-01 10:28 ` zimoun
2021-03-14 10:56 ` Ludovic Courtès
2021-03-15 9:43 ` zimoun
2021-03-17 13:54 ` Ludovic Courtès
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=87tupvtcs8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=46803@debbugs.gnu.org \
--cc=luis.felipe.la@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 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).