Wolfi APK Repository about repology-updater HOT 6 CLOSED

For the record, we could use yaml files as a data source for this repository. However, neither index nor yaml files contain upstream homepage/download URLs which are required. In addition, yaml contains ${{}} substitutions repology will not process.

from repology-updater.

I thought it would be possible to just reuse what repology is doing for alpine. But I'm new to the project itself.

from repology-updater.

I thought it would be possible to just reuse what repology is doing for alpine

It is possible, it's just that yamls contain more information. However unlike alpine, neither source for wolfi provides upstream urls which are required. For instance, U field:

C:Q1hQXyr5dHRc7y3qyEYpt4ClTH908=
P:7zip
V:22.01-r5
A:x86_64
S:854251
I:1695744
T:File archiver with a high compression ratio
U:https://7-zip.org/
L:LGPL-2.0-only
o:7zip
m:Alex Xu (Hello71) 
t:1681951026
c:1e1218a01323cd9ff429e22ac0f8d62ae9088b78
k:100
D:so:libc.musl-x86_64.so.1 ...
p:7zip-virtual p7zip=22.01-r5 ...

C:Q1WmGnNqREp8L34t7rILbINU9sMts=
P:7zip
V:22.01-r0
A:x86_64
S:1212953
I:2621828
T:File archiver with a high compression ratio
L:LGPL-2.0-only
o:7zip
t:1686942850
c:3034d595991a3a7cabd72895c1a6a723e337e478
D:so:ld-linux-x86-64.so.2 so:libc.so.6 ...
p:cmd:7zz=22.01-r0

from repology-updater.

I will try to create an issue at wolfi where the packages are built.

from repology-updater.

Wolfi does not have a concept of a "package maintainer" (m field).

We can start recording the upstream websites for packages, but the U field is not a mapping to upstream source code. It is strictly informational.

from repology-updater.

m field is not required, and there's no specific requirements for contents of U field - just any kind of URL related to upstream is needed as these are used to tell similarly named projects from each other.

However I do not suggest to change repository index format and/or introduce new data just for repologys sake. As far as I can see, upstream URLs (download locations) are present in yaml files. These contain ${{}} variable substitutions repology won't be able to expand, but if you provide compilation of these files (preferably as a single yaml or json file) with substitutions expanded that would be usable. Even preferable to APKINDEX, as these contain more useful data, such as patch files listing. On the downside, custom parser would have to be aware of uses parameters for e.g. fetch, git-checkout and patch, but these look pretty simple at the first glance. If there's no complex parsing logic hidden somewhere, it's not a problem.

from repology-updater.