all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nome Grey <greynome72@gmail.com>
To: 26608@debbugs.gnu.org, 32022@debbugs.gnu.org, 22629@debbugs.gnu.org
Subject: bug#26608: channels.scm supporting substitutes
Date: Tue, 3 Dec 2019 09:55:41 -0800	[thread overview]
Message-ID: <CANUb+mUAO2BtWebupKGSwhaNf-HnK6HgJ9JOdojV5THYWDX-5w@mail.gmail.com> (raw)
In-Reply-To: <874lxg77l4.fsf@dustycloud.org>

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

Ludovic posted some channels.scm code in September 2018 supporting using
more substitutes.  Unfortunately his code no longer functions due to an
upgrade of guile-json in guix.

I've tried to learn enough guile to upgrade the code to the newer json
structures, and posted my changes to github at
https://github.com/nomr72/guix-substitutes-channel .  It seems to run again
now.

Maybe I can learn enough to upgrade it to check the 'guix-master'
evaluations to find the latest build of key packages.  We'll see.

[-- Attachment #2: Type: text/html, Size: 734 bytes --]

  parent reply	other threads:[~2019-12-03 19:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-22 16:03 bug#26608: Provide --only-substitutes flag to "guix package --upgrade" Christopher Allan Webber
2017-04-22 23:03 ` Ludovic Courtès
2019-12-03 17:55 ` Nome Grey [this message]
2019-12-03 21:14   ` bug#26608: channels.scm supporting substitutes zimoun
2019-12-03 23:32     ` Nome Grey
2019-12-04 10:23       ` zimoun
2019-12-04 12:25         ` Nome Grey
2019-12-04 12:39           ` Nome Grey
2019-12-04 13:56             ` zimoun
2019-12-04 14:55               ` Nome Grey
2019-12-04 17:33                 ` zimoun
2019-12-04 21:50                   ` Nome Grey
2019-12-05 11:45                     ` zimoun
2019-12-05 14:35                       ` Nome Grey
2019-12-10 16:41   ` bug#32022: " 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=CANUb+mUAO2BtWebupKGSwhaNf-HnK6HgJ9JOdojV5THYWDX-5w@mail.gmail.com \
    --to=greynome72@gmail.com \
    --cc=22629@debbugs.gnu.org \
    --cc=26608@debbugs.gnu.org \
    --cc=32022@debbugs.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.