From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Leo Prikler" <leo.prikler@student.tugraz.at>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Collect guix profiles in single directory.
Date: Fri, 31 Jan 2020 14:33:11 +0100 [thread overview]
Message-ID: <87y2tnoinc.fsf@ambrevar.xyz> (raw)
In-Reply-To: <ad3a1c274a8d3cf7d31295b73e1846e39c9b22e6.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
Leo Prikler <leo.prikler@student.tugraz.at> writes:
> 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.
Yes, but I propose to go even more general: Have a configuration knob
for all files, so that everyone is free to move stuff anywhere they want.
> Conceptually it is a profile like any other.
But practically I suspect that most users will deal with it specially.
It would be nice to be able to make the distinction between the "guix"
profile and the rest.
> 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.
Indeed, we can leave this option out for now if it's too superfluous.
--
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 13:33 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
2020-01-31 13:33 ` Pierre Neidhardt [this message]
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=87y2tnoinc.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
--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).