Re: Removing directories in postrm ?
> A few of python's postinst scripts byte-compile the source files they
> install. The byte-compiled files are to be removed by the postrm scripts
> (a script removes all byte-compiled files where sources can't be found).
> Now if the python package had created a new directory, this directory is
> not empty until after postrm and won't be removed therefore.
>
> Should I keep this procedure and perhaps try to remove the directory in
> postrm with something like "(rmdir /usr/lib/python1.5/lib-tk 2>/dev/null
> || true)" ? The user still will get a warning about the non-empty
> directory.
>
> Should I come up with a solution that tries to remove the byte-compiled
> files in the prerm ? (I had to keep track of the files that were created
> in postinst).
>
> Or should I include the byte-compiled files in the packages ?
If that directory contains files generted in package's postinst, I think
you should also create that directory there, and remove it in postrm.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: