4 ms·
> I'm sure there are legitimate uses of that functionality To avoid package name pollution, e.g. having package foo, foo-newpackage, foo-newpackage-updated, et
by jolmg 2mo ago
> I'm sure there are legitimate uses of that functionality
To avoid package name pollution, e.g. having package foo, foo-newpackage, foo-newpackage-updated, etc. each by a new maintainer as the priors get abandoned.
- tremon 2mo agoWith a bit more structure, you could change that to: every package in AUR is actually registered as foo/maintainer under the hood, and installing the package without maintainer name pins it to the currently active version. Package adoption can then be formalized as a new maintainer publishing their own version of the package, and users of an already-installed package need to issue an explicit command to switch over to the new maintainer's version.
- Pay08 2mo agoOr, have actual user repos like a normal distro.
- ptx 2mo agoWhat do you mean? Their package manager allows you to add additional repositories, if that's what you want.
- yjftsjthsd-h 2mo agoHow is that different?
- jolmg 2mo agoThey do. There's a list of them on the Arch Wiki: https://wiki.archlinux.org/title/Unofficial_user_repositories https://wiki.archlinux.org/title/Unofficial_user_repositorie... The problem with user repos vs the AUR is that you're trusting the maintainer behind them instead of inspecting the PKGBUILD and fetched sources yourself.
- Pay08 2mo agoAnd they're incredibly unpopular. The entire problem is that people weren't inspecting PKGBUILDs. At least with user repositories, you have someone who can build a reputation for trustworthy packages. There's a reason why every other distro does user repos.
- deleted 2mo ago[deleted]
- Ferret7446 2mo agoAt that point just put it on github