From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: 46803@debbugs.gnu.org
Subject: bug#46803: User manual does not explain Profiles (nor GUIX_PROFILE)
Date: Sat, 27 Feb 2021 00:30:18 +0100 [thread overview]
Message-ID: <877dmube5x.fsf@nckx> (raw)
In-Reply-To: <iF0rFLFignq8SLHhbSFNXRfnWhNrlxFZsH1hTOnO1aySTkOJYuCscB6NwN3NEgq-XfM9laqzd_TE2qEhtaBYnAav09jiTNb4uAx58H7G9Ps=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Luis Felipe,
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?
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...
> Similarly, the GUIX_PROFILE variable doesn't seem to be
> defined. It seems missing from the concept and programming
> indices.
...so this part isn't unexpected.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-02-26 23:30 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 [this message]
2021-02-27 18:11 ` Luis Felipe via Bug reports for GNU Guix
2021-03-01 9:59 ` Ludovic Courtès
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=877dmube5x.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=46803@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=me@tobias.gr \
/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).