> On Tue, Oct 31, 2000 at 10:19:35AM +0200, Shaul Karl wrote:
> > The following is probably a dpkg or policy matter that I do not understand.
> > Can you explain it to me?
> >
> > [10:12:54 /tmp]$ dpkg -S /var/cache/man
> > dpkg: /var/cache/man not found.
>
> See the relevant bits from /var/lib/dpkg/info/man-db.postinst:
>
> catdir="/var/cache/man"
>
> if [ -d $catdir ]
> then echo " Removing catpages as well as $catdir hierarchy."
> rm -rf $catdir 2>/dev/null || true
> fi
>
> install -d -g root -m 02755 -o man $catdir
>
> Wichert Akkerman wrote:
> > > If man-db is responsible for /var/cache/man then dpkg should know about it.
> >
> > No.
>
> Actually, he means that it is not necessary for dpkg to know about a
> directory that a package is responsible for -- the package can create it and
> remove it in its p* scripts. As man-db does in this case.
>
Am I right that dpkg would know about this dir if it were installed during the
build of the package, say in debian/rules?
I believe that it is preferable that every system dir would be known to dpkg,
which is why I want to issue a wish bug against man-db so that the creation of
this dir would be made in debian/rules. What do you think?
> --
> Digital Electronic Being Intended for Assassination and Nullification
--
Shaul Karl <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
