From: EuAndreh via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 50606@debbugs.gnu.org
Subject: bug#50606: Add support for other formats of Guix channels
Date: Wed, 15 Sep 2021 14:30:17 -0300 [thread overview]
Message-ID: <163172701717.1270740.9988334410334115700@localhost> (raw)
As I've described in [0], one can't have a Guix channel served over Git's
"Dumb HTTP" protocol. That is caused by libgit's inability to do so [1].
Guix channel authors may want to serve channels:
- via "Dumb HTTP" Git repositories;
- via other DVCS like Mercurial, Fossil, BitKeeper;
- decoupled from the backing versioning tool.
My initial though is that making Guix knowing how to handle channels served as
tarballs would suffice, and cover all of the above. Those channels wouldn't
have the exact same caching and authentication characteristics as channels
served via Git repositories, but that seems OK.
WDYT?
[0]: https://yhetil.org/guix-user/162732098483.1190082.2428052336447457010@localhost/t/#m8bb1fc83a8eccd9819085432a59bad9257ef434a
[1]: https://github.com/libgit2/libgit2/issues/4652#issuecomment-390903142
next reply other threads:[~2021-09-15 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 17:30 EuAndreh via Bug reports for GNU Guix [this message]
2021-09-16 8:17 ` bug#50606: Add support for other formats of Guix channels 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
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=163172701717.1270740.9988334410334115700@localhost \
--to=bug-guix@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).