On Tue, 24 Aug 2004, Thomas Adam wrote: > On Tue, Aug 24, 2004 at 10:28:09PM +1000, Paul Gear wrote: > > Is it fairly common, then, that packages only create their config files, > > and don't include them in the package originally. I can see times when > > Of course it is. There are *hundreds* of files that are created in this > manner, usually brought about because they're created by the very programs in > other packages, and so there is no way of ever supplying the files in the > first place.
Or by debconf-ization of packages, which often need this. > > that would lead to confusion. Is there another way to find out where a > > file belongs? > > No, since any answer would be completely erroneous. Actually, we have been requesting this functionality to the dpkg crew for a while. It will arrive someday. The idea is that we will "register" dynamically-created stuff with a package in the maintainer script. But right now, all you can do if you *really* need to find out where a package came from is to use dpkg -L, and when that fails, try to grep for that filename in /var/lib/dpkg/info, which might or might not help. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
