From: Nicolas Graves via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Maxime Devos <maximedevos@telenet.be>, guix-devel@gnu.org
Subject: Re: Branch with only available substitutes ?
Date: Mon, 10 Jan 2022 16:04:41 +0100 [thread overview]
Message-ID: <87zgo3bp2l.fsf@ngraves.fr> (raw)
In-Reply-To: <87lezohuwv.fsf@gnu.org>
Thanks all for your answer.
Of course Maxime, wasn't meant to be mean or anything.
I'm actually willing to help, although a bit limited in time in the
coming weeks.
What would be needed to help your pending patch @Mathieu ? Not sure if
my scheme is already good enough, but I can try and take a look.
Cheers,
Nicolas
Mathieu Othacehe <othacehe@gnu.org> writes:
> Hello,
>
>> Short answer: yes, but someone has to not just ask whether it's
>> possible or tell it ‘should be easy’, and actually implement all this.
>> Also, have a look at channel-with-substitutes-available.
>> It's not sufficiently general for your use case though.
>
> There's also a pending patch extending this procedure to support
> manifests: https://issues.guix.gnu.org/47929.
>
> It still needs some work but it could be conceptually close from what
> Nicolas is asking.
>
> Mathieu
next prev parent reply other threads:[~2022-01-10 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 20:44 Branch with only available substitutes ? Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2022-01-09 23:35 ` Maxime Devos
2022-01-10 8:11 ` Mathieu Othacehe
2022-01-10 15:04 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution. [this message]
2022-01-10 10:09 ` zimoun
2022-01-10 15:16 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
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=87zgo3bp2l.fsf@ngraves.fr \
--to=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=ngraves@ngraves.fr \
--cc=othacehe@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).