John Galt <[EMAIL PROTECTED]> writes: | Would it be too hard to add a "verbose" type flag that tells exactly | what dpkg is installing as it does it? gzip does this by default, so I'd | think that since dpkg basically calls gzip, there could be a | "pass-through" switch to turn on verbose reporting with not too much | hassle. | | On Tue, 4 May 1999, William R Pentney wrote: | | > On Tue, 4 May 1999, Tommy Malloy wrote: | > | > I agree with this one. Now and then I will install a package in which none | > of the binaries have the same name as the package, and there is no manpage | > available, so I have to hunt for the application's _name_. It makes one | > feel very silly, and can be quite frustrating. | > | > I think that dselect could use an additional tool to navigate through the | > contents of packages. I realize that there is a "dpkg -l" option, but | > there must be a better way. | > | > - Bill [snip]
I'm a little confused about what you're (Tommy) asking here. Documentation for the applications that are in a package is a somewhat different issue than finding out what files a package installed. You can find all the files associated with a particular package using "dpkg -L <package>", e.g., % dpkg -L cvs /. /usr /usr/share /usr/share/doc-base /usr/share/doc-base/cvs /usr/share/doc-base/cvs-client /usr/sbin /usr/sbin/cvsconfig /usr/doc . . . Is this what you wanted? Gary
