From: EuAndreh via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, zimoun <zimon.toutoune@gmail.com>
Cc: 50606@debbugs.gnu.org
Subject: bug#50606: Add support for other formats of Guix channels
Date: Thu, 16 Sep 2021 14:41:10 -0300 [thread overview]
Message-ID: <163181407045.1503137.63518666550594558@localhost> (raw)
In-Reply-To: <CAJ3okZ2sM6is-dp0A8+9M+QN=QJDO35km_MrWHhto8XdCu0NuA@mail.gmail.com>
I agree with most points, but I'm not proposing creating integrations with other
DVCS, en par with the current Git integration.
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.
next prev parent reply other threads:[~2021-09-16 17:42 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=163181407045.1503137.63518666550594558@localhost \
--to=bug-guix@gnu.org \
--cc=50606@debbugs.gnu.org \
--cc=eu@euandre.org \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.