On Mon, Jan 31, 2000 at 07:10:02PM +1100, Brian May wrote: > *Any* file that is owned by a package must be declared by that package > to dpkg, this includes any log files, database files or configuration > files that the package might create. So, for instance, dpkg -S > /var/log/apache/access.log would return apache. This doesn't make them > installable files though, just files associated with the package.
And what about files that "belong" to multiple packages? [And, how do you ensure the fresh install of a new such package when the old one has been running for some time?] The simple solution to letting the administrator know the package which created the file (which you already see in place here) is to ensure that the path name has the package name clearly embedded. Finally, what's the difference between user files and database files? Location stored? We're currently experiencing a controversy where creation of a man page is "too much". In my opinion you're proposing a much tougher problem. -- Raul
