3 ms·
The problem with system packaging is there are so many systems. For example if you only package something for Debian, how should a Fedora, Arch, Gentoo or even
by maple3142 3y ago
The problem with system packaging is there are so many systems. For example if you only package something for Debian, how should a Fedora, Arch, Gentoo or even Mac and Windows user use that?
- seabass-labrax 3y agoDebian has by far the most rigorous packaging standards of that list, so subsequent packaging for the other distributions should not be very difficult. Bundling the dependencies into an OCI container or AppImage to run them on non-Debian systems is also trivial once you have a Debian package, but of course that comes with disadvantages. Neither Mac nor Windows have a proper first-party package manager (although winget makes some inroads, thanks of course to Keivan Beigi), so comparison becomes rather a moot point for those platforms. [1]: https://keivan.io/the-day-appget-died/ https://keivan.io/the-day-appget-died/
- nightpool 3y ago"so comparison becomes rather a moot point for those platforms." No, because the OP was comparing them to language package managers, which are widely supported on Windows
- seabass-labrax 3y agoParent said that the "problem with system packaging is there are so many systems" - emphasis mine.
- bluGill 3y agoThe problem with systems packages is they solve a slightly different problem from language packages, and so while they are closer to what is needed, they are not right either. That is one reason I didn't specify the solution.