On Tue, 2003-08-19 at 01:52, Branden Robinson wrote: > Okay. I'm glad to hear my packages (probably) weren't at fault.
No, they weren't. > dpkg -S reports only on a package's "payload"; that is, > stuff in /var/lib/dpkg/info/$package.list, not stuff created by the > package's maintainer scripts. OK, that's good to know. > Unfortunately there is no wonderful method for determining this; > essentially, you have to grep the maintainer scripts in > /var/lib/dpkg/info. Even that is not a magic bullet. I find plenty of mention of /etc...compiled, but no /usr... compiled, because it turns out that /usr/X11R6/libs/X11/xkb is symlinked to /etc...xkb. I should probably have checked that sooner... must remember to check each element in pathnames... > Dpkg provides no mechanism at present for permitting packages to > "register" additional filenames that a package doesn't unpack, but might > be interested in. Might be a good wishlist item way down the road. Hmmm... just had a really hideous idea of using something like strace for the scripts (and children thereof) to trap all creating and linking syscalls... Thanks, Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
