{"id":377,"date":"2020-10-08T14:09:21","date_gmt":"2020-10-08T13:09:21","guid":{"rendered":"http:\/\/wp.philroche.net\/?p=377"},"modified":"2020-10-08T15:50:53","modified_gmt":"2020-10-08T14:50:53","slug":"using-snaps-to-package-old-software","status":"publish","type":"post","link":"http:\/\/wp.philroche.net\/2020\/10\/08\/using-snaps-to-package-old-software\/","title":{"rendered":"Using Snaps to package old software"},"content":{"rendered":"\n

On Ubuntu Linux snaps<\/a> are app packages for desktop, cloud and IoT that are easy to install, secure, cross\u2010platform and dependency\u2010free and their main selling point is security and confinement<\/a>. <\/p>\n\n\n\n

Traditionally packaging for Ubuntu is via .deb packages but much as I try, I never find it straight forward to create or maintain deb packages and I find creating snap packages much easier. <\/p>\n\n\n\n

One use case of snaps which doesn’t get talked about much is using snaps to bring no longer supported software back to life. For example, in Ubuntu 20.10 (Groovy Gorilla) which is soon to be released there is no longer support for python2 by default and many other packages have been deprecated too in favour of newer and better replacements. This does mean though that packages which depended on these deprecated packages are not installable and will not run. Snaps can fix this.<\/p>\n\n\n\n

Snaps have the concept of Base snaps<\/a> where is snap can specify a runtime which is based on a previous release of Ubuntu.<\/p>\n\n\n\n