4 ms·
And what exactly do you mean by native packaging? AppImage? The dpkg system progresses at a snail's pace. It is hard to package for, unable to cleanly sandbox d
by melony 5y ago
And what exactly do you mean by native packaging? AppImage? The dpkg system progresses at a snail's pace. It is hard to package for, unable to cleanly sandbox dependencies, and most importantly relegates application updates to third party maintainers. If we wanted a gatekeeper between our apps and the end user, we would have become a Mac-only shop.
- CameronNemo 5y agoApplication authors can publish deb packages themselves. The tooling is not amazing for it, but plenty of people do it. Including Google Chrome, Docker, Elastic, and Kubernetes.
- smoldesu 5y agoCall me back when your packaging format can ship system daemons.
- hedora 5y agoI'm happy dpkg is stable, dedups dependencies and security updates by automatically resolving version conflicts (which is NP complete, by the way), and large communities of third party packagers provide QA and act as a line of defense against supply chain attacks. I also like how easy it is to add third party repos, so I can get software direct from larger shops. I think we want opposite things from our package managers. That may be because I'm predominantly an end user of packages, and it sounds like you develop things that get packaged. Anyway, when people say that flatpack and snap are user hostile, I generally agree, and other people that share your opinions are usually baffled.