From: Pierre Neidhardt <mail@ambrevar.xyz>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>,
Leo Prikler <leo.prikler@student.tugraz.at>
Subject: Re: [ SPAM? ] Re: Collect guix profiles in single directory.
Date: Fri, 31 Jan 2020 12:06:57 +0100 [thread overview]
Message-ID: <87ftfvq3zi.fsf@ambrevar.xyz> (raw)
In-Reply-To: <CAJ3okZ2_ToFRjaZrqpDd5R=dmSPr8yPnTgieRjd0RtP-rOxcrQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
>> 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.
>
> This environment variable already exists: XDG_CONFIG_HOME, I guess.
> See 'config-directory' in utils.scm, used by pull.scm.
Thanks for checking!
>> 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.
>
> By time creation/modification?
Any particular reason? I'm not sure this is a good approach because it
would entail that the order would change depending on the user
interaction with the profile. For instance, with profiles A and B, A
comes before B, if I update B then B would come before A.
Thoughts?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-01-31 11:07 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 ` Pierre Neidhardt [this message]
2020-01-31 9:18 ` Leo Prikler
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
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=87ftfvq3zi.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=zimon.toutoune@gmail.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 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).