From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: Reproducible profiles
Date: Sat, 16 May 2015 13:16:38 +0200 [thread overview]
Message-ID: <87egmgu609.fsf@gnu.org> (raw)
In-Reply-To: <87pp62iqmn.fsf@fsf.org> (David Thompson's message of "Thu, 14 May 2015 21:19:44 -0400")
David Thompson <dthompson2@worcester.edu> skribis:
> Lately I've been wanting to version control the list of packages that I
> install in my user profile so that I can sync it amongst many machines.
> So, I took a stab at adding a new '--apply' option to 'guix package'
> that reads in a package list from a Scheme file and creates a new
> generation of the profile with only those packages are installed.
> Here's an example configuration:
>
> (use-modules (gnu))
> (use-package-modules base less guile emacs admin ruby mail pumpio man)
>
> (list ruby
> coreutils
> less
> man-db
> notmuch
> guile-2.0
> emacs
> dmd
> offlineimap
> pumpa)
Yes, that sounds very useful.
As usual though, there’s the issue of multiple-output packages. The
above snippet is nice, but doesn’t allow you to specify a particular
output of a package.
What about instead requiring people to return a manifest:
(use-modules (guix profiles))
(use-package-modules base emacs guile)
(manifest (cons (package->manifest-entry gcc-toolchain "debug")
(map package->entry
(list gcc-toolchain emacs guile-2.0))))
That means we’ll have to document (guix profiles).
It’s more verbose than what you suggest, though. If you insist ;-), we
could allow a list of packages instead of a manifest, though I’d prefer
not to do that.
WDYT?
> Below is a naive patch that does the job, but is unideal because it
> doesn't do some nice things like display the diff between generations
> before building.
For that you would need a procedure to infer the manifest transaction:
(manifests->transaction m1 m2)
;; returns a <manifest-transaction>
and then that could be passed to ‘show-manifest-transaction’.
However, I’m not sure it’s very useful. Perhaps it would be enough to
write “installing new manifest from foo.scm with 42 entries.”
WDYT?
> I'm looking for some guidance to make this option mesh better with the
> rest of the 'guix package' utility. Any help is appreciated.
Overall it looks OK to me!
[...]
> + (option '("apply") #t #f
> + (lambda (opt name arg result arg-handler)
> + (values (alist-cons 'apply (load arg) result)
> + arg-handler)))
It would be better to delay loading until after arguments have been
parsed, as in ‘guix system’. The procedure to load the file should be
similar to ‘read-operating-system’.
We’ll need documentation and tests, too. :-)
Thank you!
Ludo’.
next prev parent reply other threads:[~2015-05-16 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 1:19 Reproducible profiles David Thompson
2015-05-16 11:16 ` Ludovic Courtès [this message]
2015-05-16 11:35 ` 宋文武
2015-05-16 20:05 ` Ludovic Courtès
2015-05-17 19:27 ` David Thompson
2015-05-22 12:02 ` 宋文武
2015-05-17 19:23 ` David Thompson
2015-05-17 20:22 ` Ludovic Courtès
2015-05-17 20:51 ` David Thompson
2015-05-18 19:28 ` Syntax for package inputs Ludovic Courtès
2015-05-18 13:38 ` Reproducible profiles David Thompson
2015-05-18 19:29 ` Ludovic Courtès
2015-05-18 21:07 ` David Thompson
2015-05-20 12:36 ` Ludovic Courtès
2015-05-20 16:14 ` David Thompson
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=87egmgu609.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--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.