From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: extend ’guix archive’?
Date: Tue, 21 Dec 2021 10:39:35 +0100 [thread overview]
Message-ID: <871r269u08.fsf@gnu.org> (raw)
In-Reply-To: <86r1a6sxc6.fsf@gmail.com> (zimoun's message of "Mon, 20 Dec 2021 23:52:41 +0100")
Hi!
zimoun <zimon.toutoune@gmail.com> skribis:
> On Mon, 20 Dec 2021 at 23:07, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Regarding nar-herder, I think it’d be nice to have a solution to
>> mirroring in Guix proper, developed similarly to other components,
>> because it could be a fairly central tool.
>>
>> ‘guix publish’ is probably not extensible enough to support that, but we
>> could make it a new ‘guix mirror’ or ‘guix sync’ or whatever command.
>
> Why not extend “guix archive”?
‘guix archive’ is a low-level tool that does very little right now; it’s
pretty far from ‘guix publish’ and related concerns.
Ludo’.
next prev parent reply other threads:[~2021-12-21 9:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 16:48 Mid-December update on bordeaux.guix.gnu.org Christopher Baines
2021-12-15 22:49 ` zimoun
2021-12-16 0:20 ` Christopher Baines
2021-12-16 11:05 ` zimoun
2021-12-16 12:48 ` Christopher Baines
2021-12-16 14:25 ` Andreas Enge
2021-12-21 9:53 ` Redundancy for source code and Disarchive Ludovic Courtès
2021-12-17 9:00 ` Mid-December update on bordeaux.guix.gnu.org Andreas Enge
2021-12-17 9:03 ` Andreas Enge
2021-12-20 22:07 ` Ludovic Courtès
2021-12-20 22:52 ` extend ’guix archive’? zimoun
2021-12-21 5:50 ` Jack Hill
2021-12-21 10:49 ` zimoun
2022-02-04 12:48 ` Christopher Baines
2021-12-21 9:39 ` Ludovic Courtès [this message]
2021-12-21 10:32 ` zimoun
2022-02-04 12:36 ` Christopher Baines
2022-01-06 13:26 ` Mid-December update on bordeaux.guix.gnu.org Christopher Baines
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=871r269u08.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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 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).