Linux Mint drops Ubuntu Snap packages

Posted Jul 9, 2020 9:15 UTC (Thu) by guus (subscriber, #41608)
In reply to: Linux Mint drops Ubuntu Snap packages by simosx
Parent article: Linux Mint drops Ubuntu Snap packages

Regarding not enough manpower to properly maintain packages: the vast majority of the packages in Debian and its derivatives require very little work; it's just a few commands for a package maintainer to download a new upstream version and have a new package version created. Also, most packages see very few changes that need to be backported. The problem is that Chrome does not have LTS releases, and they have a breakneck development pace, so it is impossible for package maintainers to backport all the bug fixes in the upstream project to the stable version in their Linux distribution. The best thing you can do is upgrade a package like Chrome to a newer upstream version. That might be fine until they also start depending on newer versions of libraries than you have in your stable distro release, because then you really won't have a stable release anymore.

The snap packages are a way to circumvent the principles of a stable distro release. I personally think it's a bad idea, because now you will never get a stable version of Chrome, you will just get the latest version that fixed the old bugs but comes with a whole bunch of new bugs. It would be much better if Chrome would have LTS releases every two years or so that the Linux distributions can sync with.

Apart from all that though, I don't see a technical reason why they couldn't make a proper deb package of the latest version of Chrome + a copy of the libraries they need, with a source version, so you can reproducibly build it, and without needing yet another package management system.

Linux Mint drops Ubuntu Snap packages

Posted Jul 9, 2020 11:39 UTC (Thu) by simosx (guest, #24338) [Link]

> The snap packages are a way to circumvent the principles of a stable distro release.

In a typical snap package, you specify the APT package of a dependency. Does not deviate much from the process in creating a deb package.

In the very special case of Chromium, a specific new version is just a branch of the upstream source code with several of the dependencies added in there.
Here is the cloned repository of Chromium that is used to create the snap package, https://code.launchpad.net/~chromium-team/chromium-browse...
The snapcraft.yaml file that creates the snap package is https://git.launchpad.net/~chromium-team/chromium-browser...

I do not know if you are packaging software in Debian or another Linux distribution. If a software is actually being developed, things change, and when you try to package a new version and you get issues, then it opens up a big fat can of worms. You may create a patch to make it work. You may communicate this patch with upstream, and then figure out whether it has been applied, fully or partially. How do you test whether the software actually works? Do you test it? Actually, it would make better sense if the developer had an installation package and have them test it themselves. Because they are more suitable to figure out if something does not work. In fact, with snap packages, a developer can use the automated Build server to create snap packages, test them, and then flip a switch to push to the Snap Store.

Linux Mint drops Ubuntu Snap packages

Posted Jul 11, 2020 9:57 UTC (Sat) by riteshsarraf (subscriber, #11138) [Link]

Similar was the case of (Oracle) VirtualBox in Debian. Post the take over of the company, the release process changed and left not much choice for its maintenance in a Debian Stable release, for example.

In my observation, there's been multiple reasons for such act.

* Competition: OEL vs RHEL. Similar situation occurred when one took over work from other, such that broken down changes were stopped being released.

* Maintenance: Maybe maintaining stable branches is too much of a hassle. And perhaps Linux LTS is just an exception to it.

* USP: Everyone wants something.