From: Leo Prikler <leo.prikler@student.tugraz.at>
To: "Pierre Neidhardt" <mail@ambrevar.xyz>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Collect guix profiles in single directory.
Date: Fri, 31 Jan 2020 10:18:15 +0100 [thread overview]
Message-ID: <ad3a1c274a8d3cf7d31295b73e1846e39c9b22e6.camel@student.tugraz.at> (raw)
In-Reply-To: <87imksoy2z.fsf@ambrevar.xyz>
Hi Pierre,
Am Freitag, den 31.01.2020, 08:59 +0100 schrieb Pierre Neidhardt:
> Hi Leo,
>
> About ordering:
>
> 1. ~/.config/guix/current is special in that it's the channel of Guix
> and it's installed by "guix pull" unlike other channels. Thus I
> don't
> think it belongs to GUIX_PROFILE_DIR. That said, we could introduce
> another environment variable for those who want to move it somewhere
> else.
The whole point of this operation was to put everything into one
directory, including profiles managed by `guix pull` rather than `guix
package` -- see the subject line and the initial post.
In the first place, current is not even some piece of configuration
that would warrant putting it into $XDG_CONFIG_DIR or requiring any
other variable, that ends with _CONFIG_DIR. Conceptually it is a
profile like any other.
> 2. Indeed profiles should be loaded in a well known order. I suggest
> to
> follow the C alphabetical order. Should "default" be sourced before
> the
> rest? Maybe not. I suggest we leave it to the user at this point.
If we use reverse alphabetical order, we'll have [z-default), default,
channels, (channels-a], which would mimic the current behaviour.
This is also beneficial when people start prefixing their profiles with
numbers to get deterministic ordering. If p00-foo is loaded after p01-
bar, the paths it sets will be so that p00-foo appears first.
> > - When GUIX_PROFILE_DIR is set, use GUIX_PROFILE_DIR/channels in
> > `guix
> > pull', falling back to ~/.config/guix/current.
>
> As suggested above, "guix pull" is quite special. I don't think we
> should put it in GUIX_PROFILE_DIR/channels.
As discussed above.
> > - When GUIX_PROFILE_DIR is set, read channels from
> > $GUIX_PROFILE_DIR/channels.scm, falling back to
> > ~/.config/guix/channels.scm.
>
> No strong opinion here, we could also leave it to
> ~/.config/guix/channels.scm. It's a configuration file after all.
Fair enough, but I'd also like $GUIX_PROFILE_DIR to be a place where
users can store their manifests and other specifications. Hence
loading channels.scm from there first (if it exists) sounds like a good
idea.
> Maybe not, since this might raise confusions, e.g. what happens when
> you
> type `-P my-profile` and there is a "my-profile" directory in the
> current directory?
My bad, I forgot, that lowercase `-p` will still exist. Now that I
think about it, is -P my-profile really that much better than -p
$GUIX_PROFILE_DIR/my-profile? I personally believe explicit to be
better here.
Regards,
Leo
next prev parent reply other threads:[~2020-01-31 9:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 10:59 Collect guix profiles in single directory Leo Prikler
2020-01-06 18:55 ` zimoun
2020-01-06 20:07 ` Alex Griffin
2020-01-06 22:52 ` zimoun
2020-01-07 13:02 ` Leo Prikler
2020-01-06 19:41 ` Pierre Neidhardt
2020-01-08 11:25 ` Ludovic Courtès
2020-01-08 13:48 ` Leo Prikler
2020-01-08 14:16 ` Pierre Neidhardt
2020-01-30 19:28 ` Pierre Neidhardt
2020-01-30 20:08 ` [ SPAM? ] " Leo Prikler
2020-01-31 7:59 ` Pierre Neidhardt
2020-01-31 8:46 ` zimoun
2020-01-31 9:29 ` Leo Prikler
2020-01-31 12:04 ` Pierre Neidhardt
2020-01-31 12:56 ` Leo Prikler
2020-01-31 13:36 ` Pierre Neidhardt
2020-01-31 11:06 ` [ SPAM? ] " Pierre Neidhardt
2020-01-31 9:18 ` Leo Prikler [this message]
2020-01-31 13:33 ` Pierre Neidhardt
2020-01-31 14:34 ` Leo Prikler
2020-01-31 15:17 ` Pierre Neidhardt
2020-01-31 15:38 ` Leo Prikler
2020-01-31 15:52 ` Pierre Neidhardt
2020-01-08 11:44 ` Raghav Gururajan
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=ad3a1c274a8d3cf7d31295b73e1846e39c9b22e6.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
/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.