From: ludo@gnu.org (Ludovic Courtès)
To: 22017@debbugs.gnu.org
Subject: bug#22017: Pinning a Guix version
Date: Thu, 26 Nov 2015 14:30:55 +0100 [thread overview]
Message-ID: <87egfcyjjk.fsf@gnu.org> (raw)
Hello!
In some cases, it’s useful to be able to pin a particular Guix version
and to use that version (see the RepPar paper for some examples.)
A naive way to do that is:
git clone …/guix.git my-pinned-guix
(cd my-pinned-guix; git checkout deadbeef)
guix package -L my-pinned-guix --manifest=my-manifest.scm
However, this is currently broken for several reasons:
1. ‘fold-packages’ recursively traverses ‘my-pinned-guix’ for .scm
files, and on its way it finds build-aux/build-self.scm,
tests/*.scm, and emacs/*.scm, which breaks it all. These
directories have to be explicitly removed before we can do
something.
Internally, ‘%package-module-path’ can have entries that are pairs
and where the cdr restricts the search of .scm files to a
sub-directory. We should expose that facility to -L and
‘GUIX_PACKAGE_PATH’ using some special syntax.
That way, one could do (say):
guix package -L my-pinned-guix,gnu/packages
meaning that only the ‘gnu/packages’ sub-directory is searched.
OTOH, it may be advisable to use the (guix …) modules from
‘my-pinned-guix’ and not just the (gnu packages …) modules, because
the former obviously contribute to the final result.
2. The ‘gnu/packages/patches’ sub-directory is not automatically added
to the search path, so in fact one has to run:
guix package -L my-pinned-guix \
-L my-pinned-guix/gnu/packages/patches …
so that patches are found. Not convenient.
3. When doing so, we get loads of:
;;; note: source file /tmp/guix/guix/build/perl-build-system.scm
;;; newer than compiled /home/ludo/src/guix/guix/build/perl-build-system.go
We should silence Guile.
4. Related to #1: since everything is evaluated, this is ~10 times
slower than the normal thing.
I think ‘guix pull’ would be a good place to add support for tagging
Guixes and similar, but it would be good if the naive approach above
would work just as well.
Ludo’.
next reply other threads:[~2015-11-26 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 13:30 Ludovic Courtès [this message]
2015-11-26 14:04 ` bug#22017: Pinning a Guix version Ludovic Courtès
2019-11-27 17:06 ` bug#22017: Bug #22017 Hunting: " zimoun
2019-11-28 8:34 ` Ludovic Courtès
2019-11-28 10:53 ` zimoun
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=87egfcyjjk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22017@debbugs.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.