unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 04 Oct 2018 09:10:35 +0200	[thread overview]
Message-ID: <875zyi191w.fsf@inria.fr> (raw)
In-Reply-To: <87zhvv5c4n.fsf@lassieur.org> ("Clément Lassieur"'s message of "Wed, 03 Oct 2018 16:38:16 +0200")

Hello,

Clément Lassieur <clement@lassieur.org> skribis:

> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>
>> Hello Guix!
>>
>> There’s a little-known but neat program that Roel Janssen wrote called
>> hpcguix-web.  It’s a web UI (with JavaScript) that allows you to browse
>> packages; the UI can be customized, and Roel’s institution, for
>> instance, customizes it to provide instructions for their clusters.  You
>> can see it in action here:
>>
>>   https://guix-hpc.bordeaux.inria.fr/browse
>>
>> Until now hpcguix-web would just allow you to browse the list of
>> packages of the Guix it was built against (it used ’fold-packages’,
>> etc.)
>
> 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.”

What we could do, though, is run hpcguix-web and Cuirass on the same
machine, and customize hpcguix-web such that it includes links to
Cuirass builds, for example.  hpcguix-web already provides a level of
customization that should make it easy.

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2018-10-04  7:10 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 [this message]
2018-10-04 17:34     ` Clément Lassieur
2018-10-05  9:15       ` Ludovic Courtès
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=875zyi191w.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).