From: Efraim Flashner <efraim@flashner.co.il>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: Hacking ideas from the Reproducible Builds Summit
Date: Wed, 8 Jan 2020 12:42:55 +0200 [thread overview]
Message-ID: <20200108104255.GB3568@E5400> (raw)
In-Reply-To: <CAJ3okZ1zdhbB6=g0LUP6071y4BqUz4v-V3yoMGhg8wZNqi6-Lg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
On Tue, Jan 07, 2020 at 06:43:54PM +0100, zimoun wrote:
> Hi Ludo,
>
> Thank you for sharing! Cool!
>
>
> > ** 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"?
>
>
> > ** TODO have ‘guix challenge’ automatically do “guix build --check” if needed (?)
>
> I like the current default. :-)
> Well, usually I do not know what I have locally build or not when I
> use "guix challenge". And time to time I use "guix challenge <pkg>" to
> know if this very <pkg> is locally built or not. Awkward but does the
> job. :-)
>
> BTW, it could be cool to expose some options of "guix build" to "guix
> challenge", e.g., "--no-substitutes", "--max-jobs", "--cores",
> "--with-source", etc.
>
I wish 'guix challenge' by default challenged all the servers in the
substitute-url list without needing to specify it with a flag and not
just the default one (berlin)
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-08 10:43 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 [this message]
2020-01-10 17:04 ` Ludovic Courtès
2020-01-08 22:04 ` Ludovic Courtès
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=20200108104255.GB3568@E5400 \
--to=efraim@flashner.co.il \
--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).