From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: pukkamustard <pukkamustard@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: (Re-) Designing extractong-downaloder
Date: Thu, 24 Feb 2022 09:50:05 +0100 [thread overview]
Message-ID: <a58fd55c-dd60-2417-a466-2ba332debe86@crazy-compilers.com> (raw)
In-Reply-To: <86y221vnrp.fsf@posteo.net>
Am 23.02.22 um 11:52 schrieb pukkamustard:
> Why use the source from hex.pm at all?
While issue 51061 is about the hex.pm importer and the rebar build
system, this thread in only about the extracting downloader :-)
> The hex.pm metadata.config file does not seem to exactly specify the
> upstream source. We would need some heuristics to figure this out. But
> maybe we could find a heuristic that works well enough? This would solve
> the double-archive problem.
FMPOV, hex.pm is one important valid distribution point for erlang and
elixir packages. Like PypPi is for Python and CPAN is for Perl. So we
should support defining this as a packages source, which can also be
used for checking for updates much easier than any git repository or
git-based forge.
Some of the packages I've investigated so far are easier to build from
hex.pm than from github. E.g. some github repos contain a „rebar“ binary
(which needs to be deleted by a snippet when defining the source), while
the corresponding hex.pm package can be used as-is.
Regarding heuristics: Since build should be reproducible, a source
definition must not use any heuristics. Anyhow this might be useful for
the hex.pm importer.
--
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:51 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 [this message]
2022-02-23 12:30 ` Maxime Devos
2022-02-23 12:35 ` Maxime Devos
2022-02-24 8:56 ` Hartmut Goebel
[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=a58fd55c-dd60-2417-a466-2ba332debe86@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=pukkamustard@posteo.net \
/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).