From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Guix-devel <guix-devel@gnu.org>
Subject: Downloader for "wrapped" tarbar?
Date: Sat, 30 May 2020 10:39:35 +0200 [thread overview]
Message-ID: <a82eee51-c4dc-05de-bac6-7ccc7efa4a85@crazy-compilers.com> (raw)
Hi,
was just written in another mail, I'm currently working on a
erlang/rebar build system. This includes an importer from hex.pm, a
package repository for elixir and erlang packages. (Since this is build
into rebar3 I assume it what PyPI is for Python and CPAN for Perl.)
At hex.pm, packages are provided in a tarfile [1] wrapping the source
tar-file:
-rw-r--r-- 0/0 1 2017-06-14 21:57 VERSION
-rw-r--r-- 0/0 64 2017-06-14 21:57 CHECKSUM
-rw-r--r-- 0/0 532 2017-06-14 21:57 metadata.config
-rw-r--r-- 0/0 4744 2017-06-14 21:57 contents.tar.gz
IMHO it does not make sense to keep this wrapping tar-file in the store.
So my idea is to create a "hexpm-fetch" method, which downloads the
tar-file and only stores the "content.tar.gz" in the store (using a
proper name, of course).
How can this be done?
[1] https://github.com/hexpm/specifications/blob/master/package_tarball.md
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next reply other threads:[~2020-05-30 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 8:39 Hartmut Goebel [this message]
2020-05-30 10:24 ` Downloader for "wrapped" tarbar? Ekaitz Zarraga
2020-05-31 8:19 ` Hartmut Goebel
2020-06-01 14:19 ` Ekaitz Zarraga
2020-05-31 8:21 ` Software heritage and " Hartmut Goebel
2020-06-01 14:12 ` zimoun
2020-06-02 19:41 ` Marius Bakke
2020-06-06 15:29 ` Hartmut Goebel
2020-06-06 17:26 ` zimoun
2020-07-06 7:37 ` Available for testing: hex.pm downloader and rebar3 build-system Hartmut Goebel
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=a82eee51-c4dc-05de-bac6-7ccc7efa4a85@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.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 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.