reassign 658222 dpkg thanks dlocate does not "mess" with any files. It makes no changes to dpkg's files whatsoever. it *reads* some of the files in /var/lib/dpkg.
On Wed, Feb 01, 2012 at 08:44:52AM +0100, Raphaël Hertzog wrote: > dlocate wants to do better than dpkg and thus accesses files which are > internal to dpkg's database and whose format you can't really rely on. > > With the landing of multiarch, the layout of files in > /var/lib/dpkg/info/ will change. "Multi-Arch: same" packages will > have an "<arch>:" prefix. > > You can use "dpkg-query --control-path" to find out the path of some > package-specific files (i.e. "conffiles", "md5sums") but you can't get the > path of ".list" because this file is not provided by the package but is i would call that a bug in dpkg, not in dlocate. dpkg *should* provide access to that file, or at least a listing equivalent to the file if it no longer exists. it's useful information that there is no excuse for hiding away from the local systems administrator. failing that, it should provide a way to list all files in all packages (preferably in some useful format like "package:filename" or even "package:arch:filename") > managed by dpkg itself and you should not have to access it. obviously, dlocate does have to access it - there's a demonstrable need and use for accessing it. craig -- craig sanders <c...@taz.net.au> BOFH excuse #46: waste water tank overflowed onto computer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
