From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Building guix-modular with cuirass
Date: Wed, 02 May 2018 15:52:25 +0200 [thread overview]
Message-ID: <876046412e.fsf@gmail.com> (raw)
In-Reply-To: <878t93nlha.fsf@gnu.org>
Hey,
> In the near future, I want ‘guix pull’ to install a ‘guix’ binary as
> opposed to simply dropping a bunch of modules in ~/.config/guix/latest.
> At that point we won’t have this kind of problem anymore.
On the same topic, as I explained in a previous email
(https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00222.html) my
main use-case for cuirass is to evaluate my manifest and build the
corresponding packages.
I could use 'cuirass-jobs' procedure and set arguments to (#:arguments
(subset . "my-package-1" "my-package-2" ...)). The drawback of this
approach is that everytime the manifest is updated, a reconfigure of
cuirass service is needed to update the package list.
I'd like to have an upstream mecanism were cuirass evaluates a local
manifest file (or even better take it from a git repository), an build
all the corresponding packages. The only configuration input from the
user would be the path of his manifest.
My first idea would be to add a piece of code in
build-aux/hydra/build-manifest.scm that would pull a manifest specified
as an argument, evaluates the packages it contains and feed it to
cuirass but that sounds a bit hacky.
Any better idea ?
Thanks,
Mathieu
next prev parent reply other threads:[~2018-05-02 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 9:10 Building guix-modular with cuirass Mathieu Othacehe
2018-04-30 13:04 ` Ludovic Courtès
2018-04-30 18:29 ` Mathieu Othacehe
2018-05-01 20:56 ` Ludovic Courtès
2018-05-02 13:52 ` Mathieu Othacehe [this message]
2018-05-09 22:05 ` Ludovic Courtès
2018-05-08 21:23 ` Nils Gillmann
2018-05-13 2:17 ` Chris Marusich
2018-05-13 7:48 ` swedebugia
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=876046412e.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.