May 2024: whatsrc.org distro status

[kpcyrd]

On 5/30/24 12:41 AM, Richard Purdie wrote:
> There is such data in Yocto Project too, although it would be spread
> into the layers that contain the software components in question.
> 
> Taking bash as an example, you can see information from the layer
> index:
> 
> https://layers.openembedded.org/layerindex/recipe/81/
> 
> which doesn't list the checksum but does point at the recipe:
> 
> https://git.openembedded.org/openembedded-core/tree/meta/recipes-extended/bash/bash_5.2.21.bb?h=master
> 
> which does list it:
> 
> SRC_URI[tarball.sha256sum] = "c8e31bdc59b69aaffc5b36509905ba3e5cbb12747091d27b4b977f078560d5b8"

Thanks!

 From a user's point of view, what's the best way to determine what's 
currently available in Yocto?

In Debian this is decided through /source/Sources.xz, in Alpine it's 
APKINDEX.tar.gz, in Arch Linux it's core.db/extra.db (although whatsrc 
uses https://gitlab.archlinux.org/archlinux/packaging/state instead).

 From what I read Yocto doesn't have this "traditional" concept of a 
package manager, do users clone this repository[1] (similar to how 
nixpkgs works) or do they download some kind of index from somewhere?

[1]: https://git.openembedded.org/openembedded-core/tree/

I'm trying to be as canonical as possible, for example with Alpine and 
WolfiOS I could also take snapshots of their aports repository[2] (or 
equivalent[3]), but instead I download and parse their APKINDEX.tar.gz 
since it records the specific git commit a package was built from.

[2]: https://gitlab.alpinelinux.org/alpine/aports
[3]: https://github.com/wolfi-dev/os

cheers,
kpcyrd