Why do people assume package managers do some form of gatekeeping?<p>It’s not the package managers who gatekeep, it’s their associated repository. People are free to create and host their own repositories (or, in Homebrew-speak, taps). Users are free to add those with no PRs involved whatsoever.
So sort of the same idea as docker where the address of a package (docker image) is built into its name. Interesting but also problematic. If a package in rhel repo is broken I can mask it with one I've built of the same name in my company repo. Since the package address isn't tied to its name, this works.
Besides features, how does this compare in daily workflow to <a href="https://asdf-vm.com/" rel="nofollow">https://asdf-vm.com/</a>? Does it provide version management or just upgrade to latest?
Am I missing something? How does this handle different package types for the same OS/Arch? Like, if I wanted to host a <i>.deb, </i>.rpm, *.appimage, etc?
# Nami<p>A decentralized binary package manager<p>### Why<p>There are already many package managers, like apt-get, brew, but this is all centralized.
Every time the author updates the software, they need to write complex configuration files and PRs and wait for merge.<p>Nami is a decentralized binary package manager,
she allows software authors to publish their software anywhere,
without having to request a merge from a software center for each update.<p>### Install<p><pre><code> $ curl -L git.io/getnami | bash && exec -l $SHELL
</code></pre>
### Usage<p><pre><code> NAME:
nami - A decentralized binary package manager
USAGE:
nami [global options] command [command options] [arguments...]
COMMANDS:
install Install package. $ nami install github.com/txthinking/nami
upgrade Upgrade package. $ nami upgrade github.com/txthinking/nami
remove Remove package. $ nami remove github.com/txthinking/nami
info Print package information. $ nami info github.com/txthinking/nami
list Print installed packages. $ nami list
help, h Shows a list of commands or help for one command
GLOBAL OPTIONS:
--help, -h show help (default: false)
</code></pre>
### Example<p><pre><code> $ nami install github.com/txthinking/nami
</code></pre>
### What Does Nami Do?<p>All files are stored in `~/.nami`<p>## Nami for Software Publisher<p>- Package name such as `yourdomain.com/package`
- Nami will send GET request to `<a href="https://yourdomain.com/package/nami.json`" rel="nofollow">https://yourdomain.com/package/nami.json`</a>, `nami.json`<p>### Built-in supported domains<p>* `github.com`: Package name such as `github.com/txthinking/nami`, put binary files in the [github releases](<a href="https://github.com/txthinking/nami/releases" rel="nofollow">https://github.com/txthinking/nami/releases</a>)<p>## License<p>Licensed under The GPLv3 License
<p><pre><code> $ curl -L git.io/getnami | bash && exec -l $SHELL
</code></pre>
When will this crap end? I can't understand how can people still do that. Everyone knows it's dangerous to pipe random scripts to bash, especially from unsecured websites, and people still suggest it as recommended way to install software...