[deleted]
Whohas – Command-line utility for cross-distro, cross-repository package search
31–40 of 42 posts
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#32Shame Homebrew for Linux is getting no love from any of the tools / lists mentioned here. Since switching to that and flatpak my distro choice is "what sticks closest to the upstream of [my preferred DE]"
Do Linux users actually use Homebrew day to day? My impression of it was that it's mostly for MacOS users that want to keep doing things the same way instead of learning the Linux way (using the OS package manager).
I use it on DSM (Synology OS) because all the software can be easily installed outside of DSM.
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#33Who has? Nixpkgs has. :) Nowadays the only search like this I need to run is nix-locate -r 'bin/foo$' It would be nice to have a CLI alternative to Repology, though.
I've been using https://search.nixos.org/ this whole time to find packages. Thanks for dropping this!
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#34I've been working on a GUI task manager for Linux and I've been wanting to put a "Funding" or ownership meta data next to the process or process group in the view so people can know where the upstream code lives, how to support the project, and what organizational unit "owns" that process. 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 c…
It already exists, the appstream spec can associate binaries with metadata.
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#35Oh nice, I just implemented something like this for installing from any package manager uv-style https://abxpkg.archivebox.io/ , but I haven't added a "search" command yet, I should add that!
Interesting, I've been wanting something like this. My main deal though is updates: how is that handled? Would love some kind of auto-update with a review/notification mechanism.
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#36First I saw that it's written in Perl. Then I realized that the last release was 11 years ago and that the repository domains are hardcoded in the one-file script.
Does it still work, though? Where else would you put the repository domains?
I would put them into a configuration file. You know, so people can configure which repositories are being searched.
Generally I advice against hard doing stuff that changes often and may need to be adjusted for different users or organizations.
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#37I've been working on a GUI task manager for Linux and I've been wanting to put a "Funding" or ownership meta data next to the process or process group in the view so people can know where the upstream code lives, how to support the project, and what organizational unit "owns" that process. 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 c…
You can usually get info about the upstream from the package metadata, e.g. on Debian:
$ apt info whohas
...
Homepage: http://www.philippwesche.org/200811/whohas/intro.html
...
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#38I've been working on a GUI task manager for Linux and I've been wanting to put a "Funding" or ownership meta data next to the process or process group in the view so people can know where the upstream code lives, how to support the project, and what organizational unit "owns" that process. 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 c…
You can usually get info about the upstream from the package metadata, e.g. on Debian: $ apt info whohas ... Homepage: http://www.philippwesche.org/200811/whohas/intro.html ... The distribution model on Linux (generally speaking) is different from Windows, though, so I don't think it makes sense to view processes as fully "owned" by the upstream in the same way as on Windows. Instead of letting each individual organi…
Packages are not binaries. When I write software for Linux I'm not gonna sit there and wait for apt whatever to run in the background. That was the whole point of the sqlite db. Don't worry I poll the entire debian database.... and ubuntu ..... and fedora.... and gentoo.... . and arch..... etc.
The tldr is binaries on linux really should have org unit as a meta data field because when I write a task manager in C it needs to be fast.
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#39I've been working on a GUI task manager for Linux and I've been wanting to put a "Funding" or ownership meta data next to the process or process group in the view so people can know where the upstream code lives, how to support the project, and what organizational unit "owns" that process. 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 c…
It already exists, the appstream spec can associate binaries with metadata.
[dead]
Re: Whohas – Command-line utility for cross-distro, cross-repository package search
#40I made this in under 100 lines bash and it supports Arch, RHEL-based, Debian-based, Alpine and OpenSuse. But the problem is that some distros just have rubbish native search of package files.
And of course my tool searches their native package manager, not their online services, API, package repos. That's a completely different approach.