From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Maxime Devos <maximedevos@telenet.be>, guix-devel <guix-devel@gnu.org>
Subject: Re: (Re-) Designing extractong-downaloder
Date: Thu, 24 Feb 2022 09:56:32 +0100 [thread overview]
Message-ID: <d63cab4e-7edb-95e1-a626-a817668c1e3d@crazy-compilers.com> (raw)
In-Reply-To: <c5a0afff23407c83957d936820a464cd2bff10d2.camel@telenet.be>
Am 23.02.22 um 13:35 schrieb Maxime Devos:
> Nevermind, this benefit is probably undone by the extra unpacking.
Probably.
Anyway, this is worth thinking of, as it would make the additional
unpacking part of the source. And thus unpacking would be decoupled from
the build-system. (Which was part of the idea behind the proposal.)
After considering this for some time, I actually like your idea: it is
explicit (which is better than implicit), flexible and simple (no
extracting downloader required at all). And it also does not lead to any
problems with content-addressed downloads like SWH. The only downside I
can see at the moment is that is stores both the outer and the inner
archive.
Let's see what others think about it.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2022-02-24 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 8:57 (Re-) Designing extractong-downaloder Hartmut Goebel
2022-02-23 10:52 ` pukkamustard
2022-02-24 8:50 ` Hartmut Goebel
2022-02-23 12:30 ` Maxime Devos
2022-02-23 12:35 ` Maxime Devos
2022-02-24 8:56 ` Hartmut Goebel [this message]
[not found] ` <beb0e29f-6066-d1b5-b560-22a3d0a98ad8@goebel-consult.de>
[not found] ` <87h77ly1ja.fsf@gmail.com>
2022-04-06 16:44 ` Designing importers (was: (Re-) Designing extracting-downloader) Hartmut Goebel
2022-04-10 20:33 ` Designing importers Ludovic Courtès
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=d63cab4e-7edb-95e1-a626-a817668c1e3d@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).