all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: ImageMagick from 2020?
Date: Wed, 19 Jan 2022 12:30:52 +0100	[thread overview]
Message-ID: <CAJ3okZ3gbi-SxPBWUkVk3G8_332BdZ=ohpngUbWCOmF2V2ZXmw@mail.gmail.com> (raw)
In-Reply-To: <87k0ewau6y.fsf@gnu.org>

Hi,

On Wed, 19 Jan 2022 at 11:36, Ludovic Courtès <ludo@gnu.org> wrote:

> > Hum, the issue is the ingestion by SWH, no?  The file 'sources.json'
> > only contains the last sources of the last revision.  And even, the
> > file 'sources.json' only contains the upstream URL, not the substitute
> > ones.
>
> Oh right, so we’ll need to feed them historical ‘sources.json’ files
> eventually, I think Timothy was planning to do that eventually.

From my side, what I would like to achieve soon:

 1- compute sources.json by CI, which means turn the current code as derivation;
 2- add the Guix fixed-output substitutes in the list of upstream.

But how to do #1 is not clear for me.  And I have never tried this #2.

Then what is also missing is:

 3- have a collection of sources.json per Guix revision -- at least
some determined by us;
 4- make the SWH nixguix loader points to this collection.

Currently, the file 'sources.json' contains the field 'revision' which
is the Guix revision (commit).  What is not clear is if the collection
is by appending or via different files.  It is a pending discussion
with SWH folks, IIRC.


Cheers,
simon


  reply	other threads:[~2022-01-19 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 17:20 ImageMagick from 2020? zimoun
2022-01-10 18:01 ` Timothy Sample
2022-01-10 18:36   ` Maxime Devos
2022-01-10 18:59     ` zimoun
2022-01-18 14:38     ` Ludovic Courtès
2022-01-18 14:49       ` zimoun
2022-01-19 10:36         ` Ludovic Courtès
2022-01-19 11:30           ` zimoun [this message]
2022-01-22 16:48             ` Timothy Sample
2022-01-24 15:00               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ3okZ3gbi-SxPBWUkVk3G8_332BdZ=ohpngUbWCOmF2V2ZXmw@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.