From: Mathieu Othacehe <othacehe@gnu.org>
To: divoplade <d@divoplade.fr>
Cc: help-guix@gnu.org
Subject: Re: Configuration for Cuirass
Date: Thu, 15 Oct 2020 10:40:41 +0200 [thread overview]
Message-ID: <87eelzq3ue.fsf@gnu.org> (raw)
In-Reply-To: <78f08542a333b6fc25b14a99f8f254ad090482a5.camel@divoplade.fr> (divoplade's message of "Thu, 15 Oct 2020 00:42:59 +0200")
Hello divoplade,
> How should I do it?
Writing the appropriate specification is quite tricky and I plan to
write a shepherd service to make it easier. In the meantime, something
like that should get you closer:
--8<---------------cut here---------------start------------->8---
(define my-packages
'((#:name . "my-packages")
(#:load-path-inputs . ("guix"))
(#:package-path-inputs . ())
(#:proc-input . "guix")
(#:proc-file . "build-aux/cuirass/gnu-system.scm")
(#:proc . cuirass-jobs)
(#:proc-args (subset "pomdappi")) ;name of the packages you want to build
(#:inputs . (((#:name . "pomdappi")
(#:url . "https://framagit.org/divoplade/pomdappi-ci.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t))
((#:name . "guix")
(#:url . "git://git.savannah.gnu.org/guix.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t))))
(#:build-outputs . ())))
(list my-packages)
--8<---------------cut here---------------end--------------->8---
If you want to use a fixed guix input, you can use the #:commit key.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-10-15 8:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 22:42 Configuration for Cuirass divoplade
2020-10-15 8:40 ` Mathieu Othacehe [this message]
2020-10-15 9:19 ` divoplade
2020-10-15 12:32 ` Mathieu Othacehe
2020-10-15 14:39 ` divoplade
2020-10-18 15:46 ` Mathieu Othacehe
2020-10-18 15:51 ` divoplade
2020-10-18 16:24 ` Mathieu Othacehe
2020-10-18 16:36 ` divoplade
2020-10-18 17:38 ` Mathieu Othacehe
2020-10-18 17:50 ` divoplade
2020-10-19 10:27 ` Mathieu Othacehe
2020-10-19 17:04 ` divoplade
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=87eelzq3ue.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=d@divoplade.fr \
--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).