From: Efraim Flashner <efraim@flashner.co.il>
To: "Gábor Boskovits" <gboskovits@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix days guix home discussion
Date: Thu, 29 Feb 2024 09:23:15 +0200 [thread overview]
Message-ID: <ZeAw447dH9sS7S3y@3900XT> (raw)
In-Reply-To: <CAAqdTgMQRz93NP8jG9FQ3UOZg_HxQzvuUd3nCjJ+_2b2RPK2tA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3288 bytes --]
On Thu, Feb 29, 2024 at 12:59:53AM +0100, Gábor Boskovits wrote:
> On guix days in the guix home discussion the following observations were
> made:
> 1. It is rare that guix home import does the right thing (it is usually
> removing some startup file customizations, does not seem to arrange to pick
> up profiles, not even its own). Either we should improve it, or document
> that it only gives a skeleton configuration and add some guidance on the
> steps needed to get a working one.
> 2. The user default profile and the home package profile being separate is
> causing some issues. It might be enough to document all the special
> profiles somewhere (which as of now include at least system profile, user
> profile, pull profile and home profile), but we can also think about a bit
> more general solution, along the lines of a home service that ensures that
> a given profile matches the supplied manifest, and have variables for the
> special profiles. (These could then provide extensions to the shell
> services which could arrange to pick them up)
In the past we had some issues with various assumptions in guix that
~/.guix-profile was the main profile and we had to add additional
use-cases for ~/.guix-home. I'm not sure if we've gotten all of them
yet.
It also might be helpful to consider something along the lines of
exposing the symlink service bits from the home service modules and see
if it would be a good idea to offer adding a symlink from
~/.guix-home/profile to ~/.guix-profile. Or (magically) adjusting
~/.guix-profile/etc/profile to also source ~/.guix-home/profile if it
exists.
> 3. Sometime on home reconfigure the shell prompt customizations seem to get
> lost. Sourcing the shell startup file fixes it. I will have to look into
> this more to file a proper bug report.
> 4. Creating a guix development environment service would be beneficial, to
> showcase the possibilities and to simplify onboarding. On top of there
> could be an additional service that adds emacs integration to this
> development environment.
Also on the topic of onboarding to guix-home, the etc-skel service now
also includes a bare-bones guix-home file. It lives in
/etc/skel/guix-home-config.scm on Guix System.
> 5. There was a recommendation to relax the expectations on the home
> services merged. Right now a lot of people are just writing services for
> private use. Most probably such a single usecase service would already be
> beneficial to multiple people. The idea is the following: make it easy for
> an initial home service to be merged. (Example: do not ask to implement
> options that the submitter is not using). Then take care that if there is
> an addition to the service that it really gets merged with what we already
> have. This needs a bit of up front design, we have to make sure that the
> services can be extended while maintaining backwards compatibility.
Seeing how often we add an extra-config field for just about every other
service I don't think that should be a hindrance.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-29 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 23:59 Guix days guix home discussion Gábor Boskovits
2024-02-29 7:23 ` Efraim Flashner [this message]
2024-03-17 17:24 ` Ludovic Courtès
2024-03-17 17:51 ` Ryan Prior
2024-03-17 21:18 ` Ludovic Courtès
2024-03-17 17:53 ` Ryan Prior
2024-03-17 21:20 ` Ludovic Courtès
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=ZeAw447dH9sS7S3y@3900XT \
--to=efraim@flashner.co.il \
--cc=gboskovits@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 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.