The issue with .deb files often involves compatibility, security, or installation problems.
The issue with .deb files often involves compatibility, security, or installation problems.
I've noticed that most recommendations suggest installing Linux programs through official software stores or the terminal. What's the issue with just downloading a .deb file from the manufacturer's site? Assuming it's a Linux version, you'd only be doing this for trusted companies that won't harm your system. From what I understand, .deb installations usually work smoothly and perform better. For instance, I struggled to get the flatpak version of MegaSync running, but the .deb worked easily. Software stores often have outdated versions, which raises concerns. Why isn't it suggested to go directly to Steam and download the .deb file? That seems safer and simpler than using the terminal. I've also heard some issues with dependencies, but the installers I used handled those automatically. I'm new to Linux for about six months, so please don't think I've missed something obvious. I'm really curious about this.
I notice the .deb/.rpm/tarballs/appimages folder as a fallback option when installation isn't possible. It's usually simpler to use the package manager and get the software from the distribution's repositories, which tend to be more secure. In Debian environments, I prioritize installing via the apt repositories—they're regularly checked for security and stability. These are .deb files, but you avoid downloading them directly from the vendor site. Next, I look for Flatpaks, then snaps, and if nothing else works, I try the official .deb from their website or appimages. Edited November 10, 2021 by RONOTHAN##
Theres nothing wrong with .deb files. debian's package manager (term = dpkg) will invoke apt-get (that software store) to resolve dependencies. There are PPAs and 3rd party repos - some include whatever updates to whatever software "deb" youre installing. you can install a ".deb" without worry, there will be no conflict or issue. The worst case is merely it not installing.
Nothing matters if you want the result the maker intended. The assembly created by the developer is most likely to be well-prepared. For a better experience, steer clear of bundled software and especially pre-made snap packages.
I believe it stems from past issues between Debian and Ubuntu compatibility. In the beginning, new users would switch to Ubuntu and then stumble upon a .deb package, only to realize it wouldn't function properly. Consequently, Ubuntu communities often warned against downloading random .deb files for software from repositories. Today it seems less urgent since many sites clearly specify which distro and version their .deb files support. Albert Launcher exemplifies this, making it nearly impossible to install the incorrect version for your system. Still, many of these concerns remain valid.
You're asking about why programs installed through deb files can be tricky to update, especially compared to updates from official software stores. This happens because the update mechanisms differ—regular updates often rely on a built-in updater, while deb packages may require manual configuration or specific tools. Regarding risks, using a deb file tailored for your distro version can still pose issues if compatibility isn't properly handled, though major companies usually aim for stability. It's important to verify the package details and ensure they match your system requirements.