From: George Clemmer <myglc2@gmail.com>
To: Divan Santana <divan@santanas.co.za>
Cc: help-guix@gnu.org
Subject: Re: Some general guix questions
Date: Tue, 08 Jan 2019 14:26:59 -0500 [thread overview]
Message-ID: <cuck1jf7xx8.fsf@gmail.com> (raw)
In-Reply-To: <87o98ryuat.fsf@santanas.co.za>
Divan Santana <divan@santanas.co.za> writes:
> Hi great guix community,
>
> 1. What is the recommendations around when to install a package system
> wide (via guix system reconfigure manifest.scm) vs in your user
> profile? I'm confused if i3/various X packages and other desktop
> packages should be installed in one or the other? Or even the pros
> and cons of each. Is this in the manual?
FWIW, when you run a single-user system (e.g. a desktop or server that
only you use), it can be convenient to install any packages that you
want available in root system-wide. E.g, I use ...
(define sys-packages
'(
"cups"
"emacs-no-x"
"emacs-guix"
"emacs-magit"
"emacs-paredit"
"freeipmi"
"git"
"glibc-utf8-locales"
"mdadm"
"mosh"
"nss-certs"
"openssh"
"qemu"
"screen"
"smartmontools"
))
...
(packages (append (map specification->package
sys-packages)
%base-packages))
> 2. One can install packages via a manifest or via a frontend tool like
> emacs-guix or helm system packages. I like the former, because
> it's like your system is defined in a manifest and evaluated, and
> you can keep track in git etc, suppose infrastructure as code. But
> I like the latter too and I believe some others do too. Is there a
> way to get the best of both worlds here? Any thoughts on the
> matter.
I find it convenient to maintain a Guix manifest under Git but I feel
free to "dabble" using emacs-guix. I "roll back" to the manifest set by
using the emacs-guix Generation-List running 'guix package -m'.
> 3. If I run guix system vm --fallback system.scm I get a vm I can run,
> which is really awesome. If I then do a guix pull and guix system
> vm --fallback system.scm I get /another/ VM which I can run. How is
> the previous VMs garbage collected, I wonder?
Your 'guix system vm' results will be protected from gc if you specify
the ‘--root=FILE’ option.
HTH - George
next prev parent reply other threads:[~2019-01-08 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:43 Some general guix questions Divan Santana
2019-01-08 17:13 ` Pierre Neidhardt
2019-01-08 20:36 ` Ricardo Wurmus
2019-01-08 21:24 ` Pierre Neidhardt
2019-01-08 21:40 ` Ricardo Wurmus
2019-01-09 18:09 ` George Clemmer
2019-01-22 10:28 ` Pierre Neidhardt
2019-01-09 7:51 ` Divan Santana
2019-01-08 19:26 ` George Clemmer [this message]
2019-01-09 7:50 ` Divan Santana
2019-01-08 20:00 ` Tonton
2019-01-09 7:48 ` Divan Santana
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=cuck1jf7xx8.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=divan@santanas.co.za \
--cc=help-guix@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.
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).