unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: George Clemmer <myglc2@gmail.com>
To: guix-devel <guix-devel@gnu.org>
Subject: [doc RFC] Tame the Guix profile blizzard?
Date: Mon, 09 Jul 2018 19:40:24 -0400	[thread overview]
Message-ID: <87tvp8q8pj.fsf@gmail.com> (raw)

ISTM our doc is a veritable "Profile Blizzard."


The term occurs 173 times in guix.texi


The "user profile" is referred to in multiple ways:

 (guix) Application Setup: "your Guix profile"

 (guix) Features: 'own “profile”', "per-user profiles", "their profile"

 (guix) Invoking guix package: "user’s own profile", "user’s default
 profile", ‘$HOME/.guix-profile’

 (guix) Invoking guix environment: "package profile"


The "system profile" is referred to in multiple ways:

 (guix) Using the Configuration System: "Globally-installed packages"

 (guix) operating-system Reference: "global profile",
 ‘/run/current-system/profile’

 (guix) Networking Services: "system profile"


An unnamed type of "environment profile" is produced by 'guix
environment'

 (guix) Invoking guix environment" ‘GUIX_ENVIRONMENT’ variable


An unnamed type of "custom profile" is produced by the 'guix package' -p
option.


(guix) Top mentions only an entirely different use of the term:

 * Invoking guix size::          Profiling disk usage.


(guix) Concept Index contains only (guix) Invoking guix package
references.


ISTM we can improve this situation as follows:

1) agree on a canonical term to use for the 4 types of profiles

2) update the doc accordingly

3) add a top level discussion of profiles

WDYT? - George

             reply	other threads:[~2018-07-09 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 23:40 George Clemmer [this message]
2018-07-10  8:54 ` [doc RFC] Tame the Guix profile blizzard? Nils Gillmann
2018-07-11  3:21   ` George Clemmer
2018-07-11  8:06     ` Nils Gillmann
2018-07-10 22:13 ` Ludovic Courtès
2018-07-11  2:52   ` George Clemmer

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=87tvp8q8pj.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=guix-devel@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).