Thomas Adam wrote: > On Tue, Aug 24, 2004 at 09:44:33PM +1000, Paul Gear wrote: > >>Hi folks, >> >>What is the canonical method for determining to which package an >>installed file belongs? dpkg -S seems to be the right *sort* of thing, >>but doesn't always work: >> >>enoch:/share/download # dpkg -S /etc/apt/apt.conf.d/70debconf >>debconf: /etc/apt/apt.conf.d/70debconf >>enoch:/share/download # dpkg -S /etc/apt/sources.list >>dpkg: /etc/apt/sources.list not found. >>enoch:/share/download # dpkg -S /etc/gpm.conf >>dpkg: /etc/gpm.conf not found. > > > It's doing *exactly* what you asked of it. Remember that dpkg -S will only > work for files that were *in* a package initially and not ones that were > *created*. /etc/apt/sources.list is created by apt-setup from 'base-config', > but does not reside in any package.
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 that would lead to confusion. Is there another way to find out where a file belongs? (I am resigned to the rest of this message being flame bait, even though it's not intended that way.) RPM's method of including the config file in the package even if it's empty or only comments seems to me a better solution - that way the config file can always be traced back to its relevant package. -- Paul <http://paulgear.webhop.net> -- If at first you *do* succeed, carefully check your success metrics for accuracy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
