ES version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 405 words in the discussion.
Trending Topics
#linux#package#search#script#though#done#api#data#process#don

Discussion (15 Comments)Read Original on HackerNews
Where else would you put the repository domains?
So I actually vibe coded a script that does this against a sqlite db I've been considering to bundle with my task manager so it can know this stuff on the fly.
But yea this is a key missing component in Linux user space. Windows let's you encode organizational stuff into an exe but on Linux binaries don't really have that.
Since switching to that and flatpak my distro choice is "what sticks closest to the upstream of [my preferred DE]"
Nixpkgs has. :)
Nowadays the only search like this I need to run is
It would be nice to have a CLI alternative to Repology, though.Abandoned, but forkable (since FOSS), and a decent idea.
Probably nowadays this gets done in Node, parsing the package search websites. Preferably, this would be done via an API though.
Repology provides an API but it's unstable: https://repology.org/api/v1
First thought, which came to my mind, was a security use case to get it to a point for sbom handling and tracking. In particular, respective to all the recent package vulnerabilities.
Go and find me all the repolists and package/software metadata for any distro and OS ever released. Write the results to a local SQLite. Incrementally update, but don't hammer the sources to death. Provide a web UI and CLI.
List of linux package search databases:
https://github.com/sxiii/awesome-package-search