Hi Valters, * Valters Jansons [2026-06-05 20:05]: >Hello, > >Currently, I have a bit of a concern for package managers and the >database file updates. > >The location tool wants to update /var/lib/location/database.db --- >however, there is also logic to bundle this file in package managers. >So, when there is a new package version, the package manager believes >it should be in charge of the file. When it looks at the update, it >sees that the "user" has made changes to the file. This results in a >conflict, and potentially a confusing message stating that the user >has made modifications to the file, while it has been automatic >updates. > >It would be nice to split it into two distinct locations - one file >being modified only by the package manager (to be used as a fallback), >and the other file being the live dynamic auto-updated choice. Has >there been any consideration for supporting such a set-up? This should already be the case in Debian. There is an initial Database shipped in libloc-database and installed into /usr/share/libloc-location/location.db: https://packages.debian.org/sid/all/libloc-database/filelist And libloc1t64 package installs a symlink by default that is outside of apt/dpkg control and can be replaces by an updated file: https://sources.debian.org/src/libloc/0.9.18-3/debian/libloc1t64.postinst#L8 It is also cleaned up again on removal: https://sources.debian.org/src/libloc/0.9.18-3/debian/libloc1t64.prerm Cheers Jochen