unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: How to create a substitute server with substitutes that failed?
Date: Thu, 27 Aug 2020 22:32:52 +0200	[thread overview]
Message-ID: <87ft87vngr.fsf@web.de> (raw)
In-Reply-To: <863648dvs6.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]


zimoun <zimon.toutoune@gmail.com> writes:

> On Wed, 26 Aug 2020 at 13:18, "Dr. Arne Babenhauserheide" <arne_bab@web.de> wrote:
>
>> What I want is just to put the required substitute archives on a server
>> for others to download. Ungoogled Chromium takes so long that only one
>> person should ever have to build it (and I need it for work, so I can be
>> that one person).
>
> Since “guix publish” does not fit your needs, this old draft [1] using
> IPFS to distribute substitutes probably neither.  But maybe your
> use-case could be an interesting test for the patch set. :-)
>
> [1]: http://issues.guix.gnu.org/issue/33899

It looks really interesting, but I’m surprised at the amount of
complexity that goes into that. I had thought that just putting files by
key would be easier.

So even with this I still haven’t seen anything to date that’s
conceptually simpler than the Gnutella Download-Mesh for swarming
downloads.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

      reply	other threads:[~2020-08-27 20:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r1rtwtes.fsf@web.de>
2020-08-26 11:18 ` How to create a substitute server with substitutes that failed? Dr. Arne Babenhauserheide
2020-08-26 12:07   ` Julien Lepiller
2020-08-26 14:56     ` Dr. Arne Babenhauserheide
2020-08-26 15:26       ` Julien Lepiller
2020-08-26 16:12         ` Dr. Arne Babenhauserheide
2020-08-26 17:00           ` Julien Lepiller
2020-08-26 20:47   ` Christopher Baines
2020-08-27  0:22     ` Dr. Arne Babenhauserheide
2020-08-27 14:10   ` zimoun
2020-08-27 20:32     ` Dr. Arne Babenhauserheide [this message]

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=87ft87vngr.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=help-guix@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.
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).