unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-devel <guix-devel@gnu.org>,
	"Clément Lassieur" <clement@lassieur.org>
Subject: Re: hpcguix-web, channels, and inferiors
Date: Thu, 11 Oct 2018 21:20:19 +0200	[thread overview]
Message-ID: <87pnwgnvd8.fsf@elephly.net> (raw)
In-Reply-To: <87bm885pwt.fsf@inria.fr>


Ludovic Courtès <ludovic.courtes@inria.fr> writes:

> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>>
>>>> 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.
>>
>> I wonder if we should work towards specifying a type for derivations.
>> This could be useful for the user interface to be able to clearly
>> distinguish grafts from full package builds.
>>
>> Currently, there’s no way to tell if the derivations listed under “These
>> derivations will be built” are expensive package builds or just simple
>> graft derivations.
>
> Indeed.  A simple trick would be to (ab)use the environment variable
> part of derivations as a property list, the way Nix has traditionally
> done it (see ‘user+system-env-vars’ in (guix derivations)).
>
> So we could have, say, a ‘hint’ environment variable, and the UI would
> use that to determine if it’s a graft.

This sounds like a good trick to me.  I think it would be great to give
more hints to the UI and make it clearer to users what work they can
expect Guix to perform.

--
Ricardo

  reply	other threads:[~2018-10-11 19:20 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
2018-10-05 11:36         ` Ricardo Wurmus
2018-10-05 16:17           ` Ludovic Courtès
2018-10-11 19:20             ` Ricardo Wurmus [this message]
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=87pnwgnvd8.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=clement@lassieur.org \
    --cc=guix-devel@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    /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).