unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Using cuirass to build your own manifest.
Date: Thu, 09 Mar 2017 13:37:13 +0100	[thread overview]
Message-ID: <87d1dqbp8m.fsf@gnu.org> (raw)
In-Reply-To: <87r328w58p.fsf@gmail.com> (Mathieu Othacehe's message of "Wed, 08 Mar 2017 09:19:02 +0100")

Hi!

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

> Here's a small tutorial on how to setup cuirass to build your own
> manifest.
>
> I see two major reasons for this kind of setup:
>
> * When you pull latest guix, hydra and bayfront may not have finished
>   building all the packages you use.
>
> * Hydra and bayfront won't build your custom packages.
>
> For this reasons I installed cuirass to build my manifest, using a
> configuration very similar to the one used on bayfront
> (http://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/bayfront.scm).

This is a very cool hack!

It might make sense to turn it into a service in GuixSD proper, because
I suspect it’s a use case that people may be interested in.  So you
would write, say:

  (service auto-build-service
           (auto-build-service-configuration
             (manifest (local-file …))
             (load-path '("/home/alice/…"))))

and it would do the right thing.  WDYT?

BTW, I think it’s the kind of experience report that would be worth
turning into a blog post on our web site.  It’s always interesting to
see how people solve specific problems with the tools.

Thanks!

Ludo’.

  parent reply	other threads:[~2017-03-09 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  8:19 Using cuirass to build your own manifest Mathieu Othacehe
2017-03-08  9:48 ` ng0
2017-03-08 14:18   ` Mathieu Othacehe
2017-03-09 12:37 ` Ludovic Courtès [this message]
2017-03-09 18:58   ` Mathieu Othacehe
2017-03-10 15:54     ` Ludovic Courtès
2017-03-10  8:55 ` Chris Marusich
2017-03-10 17:27   ` Mathieu Othacehe
2017-03-12 19:17 ` Mathieu Lirzin
2017-03-13  8:43   ` Mathieu Othacehe

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=87d1dqbp8m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).