3 ms·
Err, because it's the job of the package manager to prevent this exact situation from happening... Packages are not permitted to overwrite data files or config
by rleigh 6y ago
Err, because it's the job of the package manager to prevent this exact situation from happening...
Packages are not permitted to overwrite data files or configuration files (conffiles) from other packages. dpkg would abort the installation or upgrade of any package which tried to usurp a file owned by another package. At least, not without an explicit Replaces dependency to allow adoption of them. Enforcing consistency and ownership with a central database is the entire point of managing the system with a package manager.
This isn't even new. This is 25+ year old technology at this point.
- jcelerier 6y agoYes, and this is a behaviour that prevents various use cases, hence we need different tools with better isolation, hence docker. > Enforcing consistency and ownership with a central database is Assuming a lot of things very wrongly. My distro maintainer's idea of consistency may be very different from mine - it's not the system that matters, it's the freakin apps because running this is the only reason we buy computers for, and it happens that you need to run two apps which would be entirely incompatible on the same system (if I take my past life music production experience, for instance you really really want to keep using the same version of a software for a given project. But you can have a dozen different projects in flight which all require different versions of the software used. Try installing 12 different versions of gimp or ardour on Linux without something like appimage :))