From: George Clemmer <myglc2@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, George Clemmer <myglc2@gmail.com>
Subject: Re: [doc RFC] Tame the Guix profile blizzard?
Date: Tue, 10 Jul 2018 22:52:43 -0400 [thread overview]
Message-ID: <87k1q2eb5w.fsf@gmail.com> (raw)
In-Reply-To: <87sh4qpwms.fsf@gnu.org>
Ludovic Courtès writes:
> Hi George,
>
> George Clemmer <myglc2@gmail.com> skribis:
>
>> ISTM we can improve this situation as follows:
>>
>> 1) agree on a canonical term to use for the 4 types of profiles
>
> I think you mentioned only two types of “profiles”: one is profiles
> created by ‘guix package’ or ‘guix environment’ or ‘guix system’ (they
> are all the same kind of “profile”), and the other one is execution
> profile, which has nothing to do with that.
>
> So to me it seems that “profile” is in fact used fairly consistently,
> isn’t it?
Yes ... but ... the use of these profiles produces subtly different
"side-effects". Package operations cause changes in the user's "default"
profile that are immediately "used" in the user environment. However
'guix package -p foo' does not cause foo to be "used". 'guix
environment --ad-hoc' causes the environment profile to be "added" to
the user's environment, but --pure substitutes it for both system and
"default" profiles IIUC. IMO these could be better explained and more
easily referenced by users if we develop a structured nomenclature to
distinquish between these.
> However…
>
>> 3) add a top level discussion of profiles
>
> … we surely need this. Someone we should clearly define “profile”
> somewhere upfront. Perhaps we also need a glossary.
Agreed
prev parent reply other threads:[~2018-07-11 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 23:40 [doc RFC] Tame the Guix profile blizzard? George Clemmer
2018-07-10 8:54 ` 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 [this message]
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=87k1q2eb5w.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).