From: Divan Santana <divan@santanas.co.za>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Some general guix questions
Date: Wed, 09 Jan 2019 09:51:24 +0200 [thread overview]
Message-ID: <87ftu2z2tf.fsf@santanas.co.za> (raw)
In-Reply-To: <87muob5az4.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> 1. System-wide installation means packages are readily available to all users,
> which can be nice, but users then don't have the freedom to remove them.
> For maximal flexibility, it's often best to leave system-wide packages to the
> bare minimum and let users choose what they want.
>
> If you are preparing a distribution for an organization, requirements could
> be different. Your mileage may vary.
>
> 2. I also combine emacs-guix and helm-system-packages a lot ;)
> My personal take at this issue is to generate the manifest from all installed
> packages with the following shell script:
>
> --8<---------------cut here---------------start------------->8---
> cat<<EOF>"$PKG_ROOT/guix"
> (specifications->manifest
> '(
> EOF
>
> guix package -I | awk '{printf("\"%s", $1); if($3!="out") {printf("%s", ":" $3)}; print "\""}' | LC_ALL=C sort >>"$PKG_ROOT/guix"
> echo "))" >>"$PKG_ROOT/guix"
> --8<---------------cut here---------------end--------------->8---
>
> There might be better ways to do this.
Brilliant. Thanks Pierre.
next prev parent reply other threads:[~2019-01-09 8:07 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 [this message]
2019-01-08 19:26 ` George Clemmer
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=87ftu2z2tf.fsf@santanas.co.za \
--to=divan@santanas.co.za \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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).