From: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>
To: "Sébastien Rey-Coyrehourcq" <sebastien.rey-coyrehourcq@univ-rouen.fr>
Cc: Julien Lepiller <julien@lepiller.eu>, help-guix@gnu.org
Subject: Re: Guix home, guix system, channels, some noob questions
Date: Tue, 17 May 2022 10:57:32 +0200 [thread overview]
Message-ID: <877d6k5yf7.fsf@ruhr-uni-bochum.de> (raw)
In-Reply-To: <481369ed-182c-000c-5927-f8879503cc39@univ-rouen.fr> ("Sébastien Rey-Coyrehourcq"'s message of "Tue, 17 May 2022 10:01:52 +0200")
Hi Sébastien,
Sébastien Rey-Coyrehourcq writes:
> Thanks Daniel,
>
> So if i understand well, in the common use case, if you install guix
> home and use it in parallel with guix install, these profile are
> "cumulative",
> software installed are available no matter how I set them up (guix
> install or using guix home declarative file + reconfigure) ?
Yes, these two profiles are normally both loaded in the sense that the
shell scripts ~/.guix-profile/etc/profile and
~/.guix-home/setup-environment are sourced.
> It is a bit confusing at first for new user, what's the best workflow,
> using the guix home declarative file and "reconfigure" or directly
> guix install ?
It depends on what you want to achieve. You could use also both at the
same time. I like to use only Guix home to manage the packages that I
need on a regular basis. However, this is mainly because I also have
some dotfiles in my home-environment. If you just want to declaratively
manage the packages you use, you could also do it with manifests¹.
Additionally, sometimes, when I need a package, that I presumably only
use once, I use ‘guix shell’² for it.
Best
¹ https://guix.gnu.org/en/manual/devel/en/html_node/Writing-Manifests.html
² https://guix.gnu.org/en/manual/devel/en/html_node/Invoking-guix-shell.html#Invoking-guix-shell
--
Daniel
next prev parent reply other threads:[~2022-05-17 9:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 9:09 Guix home, guix system, channels, some noob questions Sébastien Rey-Coyrehourcq
2022-05-11 10:47 ` Julien Lepiller
2022-05-11 14:36 ` Sébastien Rey-Coyrehourcq
2022-05-11 14:55 ` Sébastien Rey-Coyrehourcq
2022-05-11 15:48 ` Julien Lepiller
2022-05-12 8:40 ` Sébastien Rey-Coyrehourcq
2022-05-12 9:28 ` Julien Lepiller
2022-05-12 12:32 ` Sébastien Rey-Coyrehourcq
2022-05-17 7:26 ` Daniel Meißner
2022-05-17 8:01 ` Sébastien Rey-Coyrehourcq
2022-05-17 8:57 ` Daniel Meißner [this message]
2022-05-17 9:20 ` Sébastien Rey-Coyrehourcq
2022-05-17 10:15 ` Daniel Meißner
2022-05-17 16:02 ` Sébastien Rey-Coyrehourcq
2022-05-25 13:34 ` Daniel Meißner
2022-05-25 18:45 ` Efraim Flashner
2022-07-11 6:06 ` Joshua Branson
2022-05-26 0:31 ` Dominic Martinez
2022-06-01 20:38 ` Sébastien Rey-Coyrehourcq
2022-06-12 19:32 ` sebastien rey-coyrehourcq
2022-06-13 19:31 ` Dominic Martinez
2022-06-14 10:36 ` Sébastien Rey-Coyrehourcq
2022-05-11 21:56 ` Mekeor Melire
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=877d6k5yf7.fsf@ruhr-uni-bochum.de \
--to=daniel.meissner-i4k@ruhr-uni-bochum.de \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=sebastien.rey-coyrehourcq@univ-rouen.fr \
/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.
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).