From: "Ludovic Courtès" <ludo@gnu.org>
To: EuAndreh <eu@euandre.org>
Cc: 50606@debbugs.gnu.org
Subject: bug#50606: Add support for other formats of Guix channels
Date: Thu, 16 Sep 2021 22:21:40 +0200 [thread overview]
Message-ID: <878rzwz2y3.fsf@gnu.org> (raw)
In-Reply-To: <163181407045.1503137.63518666550594558@localhost> (EuAndreh's message of "Thu, 16 Sep 2021 14:41:10 -0300")
EuAndreh <eu@euandre.org> skribis:
> My proposal was a little more crude: get the channel code from a tarball. In
> this model there are no authentications with fingerprint or signed commits,
> neither "guix pull" would know much about the before/after state of a channel
> besides comparing the checksum of the whole tarball.
>
> This lower level abstraction is much less sofisticated, and would probably mean
> refetching and rebuilding from tarball-backed channels than Git channels. But
> this also means that the requirement is lower, and much more universal: a
> tarball file served over HTTP, compared to a specific Git HTTP protocol.
Note that we already have -L and GUIX_PACKAGE_PATH as an alternative to
full-blown channels. I’d recommend using that when in need of a
lightweight alternative. How does that sound?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-09-16 20:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 17:30 bug#50606: Add support for other formats of Guix channels EuAndreh via Bug reports for GNU Guix
2021-09-16 8:17 ` Ludovic Courtès
2021-09-16 11:18 ` zimoun
2021-09-16 17:41 ` EuAndreh via Bug reports for GNU Guix
2021-09-16 17:48 ` EuAndreh via Bug reports for GNU Guix
2021-09-16 17:51 ` EuAndreh via Bug reports for GNU Guix
2021-09-16 20:21 ` Ludovic Courtès [this message]
2021-09-17 10:41 ` EuAndreh via Bug reports for GNU Guix
2021-09-17 10:46 ` EuAndreh via Bug reports for GNU Guix
2021-09-17 17:00 ` zimoun
2021-09-18 10:08 ` Ludovic Courtès
2021-09-16 23:44 ` Leo Famulari
2021-09-17 8:16 ` zimoun
2021-09-17 10:44 ` EuAndreh via Bug reports for GNU Guix
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=878rzwz2y3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50606@debbugs.gnu.org \
--cc=eu@euandre.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).