No, I meant to ask what I asked. Some .deb files will add their repository. Others HAVE a repository, but it must be added by hand. If the user is going to a) install a deb and b) have a repository added, why do some devs not include adding the repository in the .deb, thus reducing steps and risk of human error in adding the repo?
Ah, I see what you mean.
I'm just guessing here but maybe is to avoid problems if and when the user updates the operating system to a higher LTS version. Repositories aim at specific versions of Ubuntu like focal, jammy, etc. If the user upgrades without also making sure these are upgraded, it can cause problems.
Google Chrome is a good example of this, as it explicitly informs the user at the download prompt that the repository will be added and provides instructions on how to prevent this.
1 Like
A post was merged into an existing topic: GNOME software store immediately crashes after launching in zorin17.x
.appimage is still a standalone product requiring updates outside the system.
Plus I posted a tutorial on how to remove flatpak and snap.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.