From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: guix-devel@gnu.org
Subject: Multiple profiles with Guix Home
Date: Sun, 03 Oct 2021 12:50:33 +0200 [thread overview]
Message-ID: <adfff0005ab64c9c2c748d4a8e7f5a7a644b229f.camel@gmail.com> (raw)
Hi Guix,
it's been a while since the discussion of whether or not to collect
multiple profiles into a single directory [1]. This suggestion takes
inspiration from that, but goes a vastly different route. Instead of
using environment variables to control Guix, it takes advantage of the
recently added Guix Home, even if it is still a technical preview.
So, what's the proposition? I suggest we modify home-profile-service-
type (or add a new service) such that it takes a list of <home-profile>
records instead of a list of packages. This record would be defined as
(define-record-type* <home-profile> home-profile
make-home-profile home-profile? this-home-profile
(location home-profile-location) ; string, e.g. $HOME/.guix-profile
(short-name home-profile-short-name) ; string or #f, if given
; construct a symlink in
; /var/guix/.../per-user/
(manifest %home-profile-manifest) ; <manifest> or #f
(packages home-profile-packages) ; list of <package> or #f
; fallback for manifest
(enabled? home-profile-enabled?) ; boolean, default #t
[...])
(define (home-profile-manifest home-profile)
(or (%home-profile-manifest home-profile)
(and=> (home-profile-packages home-profile)
packages->manifest))))
On init/reconfigure, `guix home' creates/updates all home-profiles
which have a home-profile-manifest that is not #f and links them to the
appropriate locations. It also creates a shell startup script that
loads those profiles that are enabled?, even if they have no manifest
(this can be used to e.g. declare a pull profile, which `guix home'
can't manage).
Some existing home services would need to be adapted towards this
multiple profile usage. For instance, home-fontconfig-service-type
would need to accept a list of directories, rather than hardcode its
value.
What do y'all think?
<https://lists.gnu.org/archive/html/guix-devel/2019-12/msg00358.html>
next reply other threads:[~2021-10-03 10:51 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 10:50 Liliana Marie Prikler [this message]
2021-10-04 7:17 ` Multiple profiles with Guix Home zimoun
2021-10-04 8:11 ` Liliana Marie Prikler
2022-05-03 14:13 ` Andrew Tropin
2022-05-03 18:34 ` Liliana Marie Prikler
2022-05-03 19:13 ` Maxime Devos
2022-05-03 20:04 ` Liliana Marie Prikler
2022-05-03 20:39 ` Maxime Devos
2022-05-03 20:44 ` Maxime Devos
2022-05-04 9:25 ` Maxime Devos
2022-05-03 20:59 ` Maxime Devos
2022-05-04 4:16 ` Liliana Marie Prikler
2022-05-04 7:01 ` Maxime Devos
2022-05-04 7:08 ` Maxime Devos
2022-05-04 13:15 ` Reza Housseini
2022-05-04 13:46 ` Maxime Devos
2022-05-04 18:14 ` zimoun
2022-05-04 18:21 ` Maxime Devos
2022-05-05 8:01 ` Andrew Tropin
2022-05-04 18:38 ` Liliana Marie Prikler
2022-05-04 20:41 ` Maxime Devos
2022-05-05 4:25 ` Liliana Marie Prikler
2022-05-05 10:53 ` Maxime Devos
2022-05-05 16:24 ` Liliana Marie Prikler
2022-05-05 16:33 ` Maxime Devos
2022-05-05 17:21 ` Liliana Marie Prikler
2022-05-05 17:29 ` Maxime Devos
2022-05-05 11:03 ` Maxime Devos
2022-05-05 16:31 ` Liliana Marie Prikler
2022-05-05 16:42 ` Maxime Devos
2022-05-05 17:12 ` Maxime Devos
2022-05-05 17:27 ` Liliana Marie Prikler
2022-05-05 17:41 ` Maxime Devos
2022-05-05 19:17 ` Liliana Marie Prikler
2022-05-05 19:42 ` Maxime Devos
2022-05-05 20:20 ` Liliana Marie Prikler
2022-05-05 18:00 ` Maxime Devos
2022-05-05 19:08 ` Liliana Marie Prikler
2022-05-05 19:44 ` Maxime Devos
2022-05-05 23:53 ` zimoun
2022-05-05 20:13 ` Maxime Devos
2022-05-05 20:53 ` Liliana Marie Prikler
2022-05-05 21:28 ` Maxime Devos
2022-05-06 4:19 ` Liliana Marie Prikler
2022-05-07 23:06 ` Ludovic Courtès
2022-05-05 20:50 ` zimoun
2022-05-05 18:25 ` zimoun
2022-05-03 21:11 ` Maxime Devos
2022-05-04 4:23 ` Liliana Marie Prikler
2022-05-04 6:57 ` Maxime Devos
2022-05-04 9:24 ` Maxime Devos
2022-05-04 13:05 ` Andrew Tropin
2022-05-05 11:05 ` Maxime Devos
2022-05-05 16:22 ` Liliana Marie Prikler
2022-05-05 17:07 ` Maxime Devos
2022-05-05 17:19 ` Liliana Marie Prikler
2022-05-05 17:29 ` Maxime Devos
2022-05-05 18:24 ` Liliana Marie Prikler
2022-05-05 20:14 ` Maxime Devos
2022-05-05 20:27 ` Liliana Marie Prikler
2022-05-05 20:38 ` Maxime Devos
2022-05-05 20:41 ` Maxime Devos
2022-05-05 20:26 ` Maxime Devos
2022-05-06 18:40 ` Liliana Marie Prikler
2022-05-06 19:54 ` Maxime Devos
2022-05-06 21:32 ` Liliana Marie Prikler
2022-05-07 7:17 ` Maxime Devos
2022-05-23 13:14 ` Andrew Tropin
2022-05-23 17:05 ` Liliana Marie Prikler
2022-05-24 11:55 ` Andrew Tropin
2022-05-24 18:31 ` Liliana Marie Prikler
2022-05-25 11:01 ` Andrew Tropin
2022-05-25 23:36 ` Liliana Marie Prikler
2022-05-27 12:52 ` andrew
2022-05-27 13:14 ` Liliana Marie Prikler
-- strict thread matches above, loose matches on Subject: below --
2021-10-03 20:51 John Kehayias
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=adfff0005ab64c9c2c748d4a8e7f5a7a644b229f.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--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).