unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: Hacking ideas from the Reproducible Builds Summit
Date: Wed, 08 Jan 2020 23:04:33 +0100	[thread overview]
Message-ID: <87ftgpd2q6.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ1zdhbB6=g0LUP6071y4BqUz4v-V3yoMGhg8wZNqi6-Lg@mail.gmail.com> (zimoun's message of "Tue, 7 Jan 2020 18:43:54 +0100")

Hi!

zimoun <zimon.toutoune@gmail.com> skribis:

>> ** TODO make it easy to run CI
>>   - “guix ci -C channel.scm -m manifest.scm”
>
> Do you a pointer (thread in guix-devel or bug) about this point "guix ci"?

It was just discussed there.  We were saying that reproducibility and
‘guix challenge’ & co. are useful only if people actually run CI
services, and can thus compare their results with one another.  We have
‘guix publish’, which is rather easy to run, but Cuirass is quite
complex to set up.

If, instead, you could run a simple command like the one above, it’d be
much easier for each one of us to build stuff and publish results.

>> ** TODO have ‘guix challenge’ automatically do “guix build --check” if needed (?)
>
> I like the current default. :-)

Actually I like it too :-), but it makes sense to think about how we can
better integrate all the tools and options that test reproducibility.

Thanks,
Ludo’.

      parent reply	other threads:[~2020-01-08 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 15:40 Hacking ideas from the Reproducible Builds Summit Ludovic Courtès
2020-01-07 17:43 ` zimoun
2020-01-08 10:42   ` Efraim Flashner
2020-01-10 17:04     ` Ludovic Courtès
2020-01-08 22:04   ` Ludovic Courtès [this message]

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=87ftgpd2q6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=Guix-devel@gnu.org \
    --cc=zimon.toutoune@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).