> >I heartily agree with Daniel's plea. Eveb a simple listing of what
> >configuration files the package uses (and where they are), and where it
> >stores data (i.e., does it use space in /var) would be a big help.
> less /var/lib/dpkg/info/<package>.list
>
> If you really care, write a nice wrapper users can use to read the file.
Uhm, how about.. ?
dpkg-l()
{
dpkg -L $1
}
=)