.snap Vs .deb Package
In this post, we will show you big differences between .deb and .snap packages.
Debian packages are sets of content files necessary to implement commands or features needed by users to solve an issue.
To install from the command line, normally we use an elevated command, like the one bellow, if the file is locally located.
dpkg provides the basic functionality for installing and manipulating Debian packages. Generally users don’t manage packages manually, instead, they use APT package management software.
Signed packagesDebian-based distributions support GPG signature verification of signed Debian packages but this is not set by default. As a workaround, repository metadata is used to verify the authenticity of the file.
- To update, you need to have a PPA.
- If you have a .deb package you can install it by double-clicking it.
- .deb files are not very secure since they can have access to everything on your computer.
- It shares libraries with other installed applications.
To have it running on your system you only have to install snapd on your system.
- Simple to package leveraging your existing tools.
- Automatic updates for everyone.
- Reach tens of millions of Linux systems.
- Roll back versions effortlessly.
- Integrate easily with build and CI infrastructure.
- Free for open and closed source projects.
- Snaps are quick to install from GNOME Software or the command line.
- Snaps update automatically and transactionally so your app is always fresh.
- Snaps stay secure as they are confined from the OS, other apps, and hardware functions.
- You can revert snap to an earlier state if the snap fails.
Many Distros are already using snap packaging including fedora and Debian.
There are 3 types of confinement for snap packages.
This is the default confinement for all apps. It gives the application read and writes permissions only in its install folder and if a home plug or interfaces are available for the app, users are also capable of accessing the home folder.
Strict confinement gives you the following readable and/or writable paths:
- /snap/<snap>/<revision> (read-only, snap install path).
- /var/snap/<snap>/<revision> (read/write, per-revision data).
- /var/snap/<snap>/common (read/write, common data).
- /home/$USER/snap/<snap>/<revision> (read/write, per-revision user data).
- /home/$USER/snap/<snap>/common (read/write, common user data).
Used for developers to test their applications. Snaps in developer mode cannot be released in stable mode. For them to be able to release, the developer must change strict mode or classic and then change to stable or candidate snap stores channels.
Classic snaps are snaps that work the same way .deb packages work, without any confinement.
Snap apps with this confinement can go beyond home folder access – it can read and write on root folders.
Although applications can have classic confinement it doesn’t mean that every application can have this confinement. For an application to have this confinement your application needs to be approved by a team at snapcraft.io after the reasons for classic confinement are agreed by all members of the team.
Snaps have many advantages over deb packages, regarding security and updates. With snaps, you can have up to date applications because it ships with its own libraries not needing system library to run.Support for transactional updates let you download only the part that changed on your application.
Leave your feedback on what would you choose for your applications – deb or snaps?