From: ludovic.courtes@inria.fr (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: hpcguix-web, channels, and inferiors
Date: Fri, 05 Oct 2018 11:15:14 +0200 [thread overview]
Message-ID: <87zhvs69gd.fsf@inria.fr> (raw)
In-Reply-To: <87sh1l62ge.fsf@lassieur.org> ("Clément Lassieur"'s message of "Thu, 04 Oct 2018 19:34:09 +0200")
Hi,
Clément Lassieur <clement@lassieur.org> skribis:
> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>
>> Hello,
>>
>> Clément Lassieur <clement@lassieur.org> skribis:
[...]
>>> Would it make sense to integrate it into Cuirass? We could browse
>>> packages on Cuirass and to each package would be associated a link to
>>> its build status on different architectures, etc.
>>>
>>> What do you think?
>>
>> Good question. Some sort of integration is desirable, with links as you
>> mention. Now Cuirass is not specifically about packages, conceptually
>> at least, so IMO having both features in the same tool would “break the
>> abstraction.”
>
> Yes I agree. I wonder though: is there a way to know if a specific
> derivation is a package?
In general no. Of course one could play trick to try and guess whether
it corresponds to a package, but that should be avoided IMO.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-10-05 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 13:18 hpcguix-web, channels, and inferiors Ludovic Courtès
2018-09-11 10:24 ` Pierre Neidhardt
2018-09-11 12:19 ` Ricardo Wurmus
2018-10-03 14:38 ` Clément Lassieur
2018-10-04 7:10 ` Ludovic Courtès
2018-10-04 17:34 ` Clément Lassieur
2018-10-05 9:15 ` Ludovic Courtès [this message]
2018-10-05 11:36 ` Ricardo Wurmus
2018-10-05 16:17 ` Ludovic Courtès
2018-10-11 19:20 ` Ricardo Wurmus
2018-10-12 15:58 ` Estimating build time Ludovic Courtès
2018-10-12 23:13 ` Clément Lassieur
2018-10-13 10:48 ` Pierre Neidhardt
2018-10-14 7:16 ` Efraim Flashner
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=87zhvs69gd.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=clement@lassieur.org \
--cc=guix-devel@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.
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).