What? :-)
Apt is by far the easiest way o install and keep software updated.
Compared to app-store, homebrew, and toy like solutions for Windows.
What? :-)
Apt is by far the easiest way o install and keep software updated.
Compared to app-store, homebrew, and toy like solutions for Windows.
The main issue with distro-centric package formats like deb/rpm is they come from a pre-containers/pre-sandboxing era.
Their most ergonomic usage is installing distro-blessed software system-wide, where you trust the distributor to have ensured it's not some malware or other nefarious junk.
When it comes to installing software directly provided by third-parties, open or closed, there's a strong need for sandboxing integration at the package level. And once you're sandboxing instances of software, you start needing things like portals to access your files and devices outside the sandbox.
If a third-party has provided you with a .deb or .rpm, what's to prevent that package's privileged hooks from doing harm when you install it via dpkg/apt/rpm as root? Let alone the installed software potentially being malicious, the packaging itself can do serious damage.
This is a big part of why stuff like flatpak exists today.
The format is likely to give Linux users a slightly more BSD-ish separation between core system software and third-party applications, going forward. So 'avoid mucking about with third-party DEB and RPM files' is likely to become a rule of thumb for end users.
I'm no flatpak dev, nor am I intimately familiar with its implementation. But with little effort glancing at the code one can confirm there's clearly effort to even sandbox triggers:
https://github.com/flatpak/flatpak/blob/1.15.3/common/flatpa...
Note that flatpak builds upon bubblewrap, which descends from linux-user-chroot, a project specifically focused on preventing things like host contamination during package builds over tools like jhbuild. The devs are aware of these issues and aspire to address them.
I doubt it's perfect though, and I'm sure there are insecure modes for flatpaks where everything just occurs in the host namespace. But hopefully that's made clear to the end-user before proceeding. I recall there being some brouhaha over flathub misrepresenting some apps as totally secure/sandboxed which shouldn't have been, because they were still running in the host namespace or something like that. I believe that got fixed though.
There can never be a package system where you can safely install malware.
Trying to do so has now muddied the process, pushing developers away from learning how to properly package applications, if at all. .appimage makes them obsolete anyways. If I want to distribute malware I don't need a .Deb to do it.
Downloading individual DEB files is not a great way to go, but if you must, you're better off using something like gdebi than dpkg to install them. If you use gdebi, apt will still try to resolve dependencies when installing the package for you. With dpkg, you have to do all of that manually, so dpkg is only useful for installing the worst kinds of DEB files (ones that ignore the real packaging system and bundle all of their dependencies).
If you only want the command line utility instead of the GUI DEB file handler, grab gdebi-core.
I also wanna return to this, briefly:
> not exactly something you can find out without dedicated research.
It bugs the hell out of me that some distros (like the Debian that comes on WSL, for example) does not include absolutely basic Unix essentials like the man command and friends. Because this shouldn't be something that takes extended research. The old Unix tools for documenting the system internally can handle this perfectly! If you run
apropos deb
you will get a nice short list of things used for working with DEB files, including dpkg. So even if it's not the best tool it should be at least enough to find something for working with those files, without having to Google around for a long time or install any new software.The organization of Windows malware creators would like to thank you for your idea. /s.
DEB is an archive format.
So the Linux desktop ecosystem as a whole doesn't necessarily know ahead of time which way you want to use a DEB file.
Of course, an archive manager which can detect whether you're on a Debian-based system or not, and appropriately choose whether or not to show you an 'install' button after opening the archive, is very much possible and would be quite nice.
I have more than a handful of gripes about Windows, but I can at least say that clicking an .exe has a very clearly defined and understandable behavior.