From: Luis Felipe via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 46803@debbugs.gnu.org
Subject: bug#46803: User manual does not explain Profiles (nor GUIX_PROFILE)
Date: Fri, 26 Feb 2021 21:24:41 +0000 [thread overview]
Message-ID: <iF0rFLFignq8SLHhbSFNXRfnWhNrlxFZsH1hTOnO1aySTkOJYuCscB6NwN3NEgq-XfM9laqzd_TE2qEhtaBYnAav09jiTNb4uAx58H7G9Ps=@protonmail.com> (raw)
The Guix reference manual does not seem to explain what profiles are.
## Steps to reproduce
Assuming you are browsing the Guix reference manual in Info:
1. Type i (to search for an index topic).
2. Type the word profile and hit Enter.
3. Type , repeatedly to explore all the parts of the manual related to profiles.
## Expected result
At some point, I get to a section defining what is a profile exactly, a profile of what, what can I get from using one or many of them, what is the GUIX_PROFILE variable, does it accept a single path to a profile or more, and some use cases and examples.
## Unexpected result
I see profiles are mentioned in places where they can be used, but the text assumes I know what a profile is.
Similarly, the GUIX_PROFILE variable doesn't seem to be defined. It seems missing from the concept and programming indices.
## Additional information
The "Guix Profiles in Practice" recipe in the cookbook defines profiles to some extent. Maybe some of this information can be used in the manual?
---
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/
next reply other threads:[~2021-02-26 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 21:24 Luis Felipe via Bug reports for GNU Guix [this message]
2021-02-26 23:30 ` bug#46803: User manual does not explain Profiles (nor GUIX_PROFILE) 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='iF0rFLFignq8SLHhbSFNXRfnWhNrlxFZsH1hTOnO1aySTkOJYuCscB6NwN3NEgq-XfM9laqzd_TE2qEhtaBYnAav09jiTNb4uAx58H7G9Ps=@protonmail.com' \
--to=bug-guix@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 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.