From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: zimoun <zimon.toutoune@gmail.com>,
simon tournier <simon.tournier@univ-paris-diderot.fr>,
guix-devel@gnu.org, guix-hpc@gnu.org
Subject: Re: Reproducible Research Hackathon: Friday, July 3rd
Date: Fri, 03 Jul 2020 18:56:20 +0100 [thread overview]
Message-ID: <662bb1846a48ec78c594d594f14a76aee621ab9e.camel@tourbillion-technology.com> (raw)
In-Reply-To: <86fta8cyna.fsf@gmail.com>
Hi Simon,
Thank you for organising the day.
> We are interested to hear your feedback. Especially about what pass,
> what fail and what you have learnt, if you enjoyed the experience, or on
> the contrary if you not, what could be improved for the next round.
One outstanding puzzle for me is to figure out how to test a package
definition in a new channel. For example, I have cloned the guix-past
repository and started to add a new package. However, what is the best
workflow to attempt a build from the channel? Do you add the channel
to the git checkout of guix?
Best regards,
Paul.
next prev parent reply other threads:[~2020-07-03 17:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 12:40 Reproducible Research Hackathon: Friday, July 3rd simon tournier
2020-07-01 4:57 ` Pjotr Prins
2020-07-01 9:10 ` zimoun
2020-07-01 9:21 ` Efraim Flashner
2020-07-03 17:10 ` zimoun
2020-07-03 17:36 ` Ricardo Wurmus
2020-07-03 17:56 ` Paul Garlick [this message]
2020-07-03 18:19 ` zimoun
2020-07-07 17:52 ` Paul Garlick
2020-07-03 21:17 ` Ricardo Wurmus
2020-07-07 17:44 ` Paul Garlick
2020-07-04 9:51 ` Konrad Hinsen
2020-07-13 13:41 ` Ludovic Courtès
2020-07-14 8:13 ` Konrad Hinsen
2020-07-14 8:54 ` Bonface M. K.
2020-07-14 19:53 ` Konrad Hinsen
2020-07-14 13:18 ` 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=662bb1846a48ec78c594d594f14a76aee621ab9e.camel@tourbillion-technology.com \
--to=pgarlick@tourbillion-technology.com \
--cc=guix-devel@gnu.org \
--cc=guix-hpc@gnu.org \
--cc=simon.tournier@univ-paris-diderot.fr \
--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).