unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: guix-devel@gnu.org
Subject: Collect guix profiles in single directory.
Date: Mon, 23 Dec 2019 11:59:45 +0100	[thread overview]
Message-ID: <eabe0cccdb377b1c573df88715d6aebf7bf7f80c.camel@student.tugraz.at> (raw)

Hello Guix,

currently, our configuration is (more or less true to XDG) scattered
around various places.  Even if one does not make use of more advanced
features, one will at least have two profiles:
- ~/.config/guix/current
- ~/.guix-profile
If one does have more configuration data, the channels.scm must be put
under ~/$XDG_CONFIG_HOME/guix/.  Note, that this need not be
~/.config/guix, but most likely is.  If one wishes to use more than one
profile, so as to keep the build times for each shorter, one has to
write custom code and can not rely on /etc/profile.

This is a proposal to change the current approach.  Instead of
splitting Guix config in a way that tries to conform to XDG, but does
not really, I propose to use a single directory ~/.guix for all
configuration.
This includes:
- ~/.guix/channels.scm
- ~/.guix/channels (instead of ~/.guix/current, to match the name
channels.scm)
- ~/.guix/profile
- user-generated profiles

/etc/profile would be rewritten to assume that all subdirectories of
~/.guix are profiles, but loading ~/.guix/channels at last, as is the
current behaviour.  In addition, the crucial variables, that are
exported manually for #20255 and #24445 would also have to be taken
into account here.

I think, that these changes would make working with multiple profiles a
lot easier, as all profiles in that directory would then be considered
equal (with the exception of channels).  Additionally, a command could
be provided to operate on all profiles at once, to allow cumultative
upgrades, roll-backs, etc. although that might as well be done through
user scripts (that they could also put into ~/.guix).

WDYT?

Regards,
Leo

             reply	other threads:[~2019-12-23 10:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 10:59 Leo Prikler [this message]
2020-01-06 18:55 ` Collect guix profiles in single directory 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
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=eabe0cccdb377b1c573df88715d6aebf7bf7f80c.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --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).