[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Designing importers (was: (Re-) Designing extracting-downloader)

From: Hartmut Goebel
Subject: Designing importers (was: (Re-) Designing extracting-downloader)
Date: Wed, 6 Apr 2022 18:44:06 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0

Am 26.03.22 um 01:56 schrieb Maxim Cournoyer:

[Answering on the question how to design the extracting download I originally thought of using got packages:]

Is there a strong reason to want to use the archive instead of the
sources from the project repository?

For the same reason you prefer to import from a PyPI package instead of the project git-repo: The metadata is easily available.

Anyhow, using the git-repo could be a pro, since the package might miss tests or test-data. OTOH I discovered that some Erlang projects have the build-tool binary („rebar3“)  committed in the git-repo, So when using the git-repo, this needs to be removed by a snippet (which would not be required when using the archive).

So this is a more general discussion: Would it be better — also in regard to detecting new versions — to use the projects source-repo or the package manager's repo.

Given the recent discussion about how to make packaging easier, maybe the importer (and others) should become much more capable: E.g. the importer could fetch the meta-data from and then create a package definition pointing to github (falling back to And then - to make life easy for packagers, check the repo for „rebar3“ and in case create a snippet for removing it.

Hartmut Goebel

| Hartmut Goebel          |               |
| | compilers which you thought are impossible |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]