On Tue, Oct 14, 2008 at 08:34:06PM -0000, Tim Gardner wrote:
> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
> intrepid.git;a=commit;h=5b28a2ae632698758bf84364a5d87c6fcaaff03b
>
> postrm will still cleanup the depmod created modules files, even though
> they are no longer shipped in the linux-image package. This seems like
> it might be a violation of Debian policy, but it also seems benign.
Which part of policy are you concerned about? On its face, this seems
precisely correct.
postrm should unwind the changes which are made by maintainer scripts during
installation. It is explicitly not responsible for removing files which are
contained in the .deb: dpkg does this itself.
So if the depmod output is created in postinst, removing it in postrm is the
right thing to do.
On Tue, Oct 14, 2008 at 08:34:06PM -0000, Tim Gardner wrote: kernel. ubuntu. com/git? p=ubuntu/ ubuntu- git;a=commit; h=5b28a2ae63269 8758bf84364a5d8 7c6fcaaff03b
> http://
> intrepid.
>
> postrm will still cleanup the depmod created modules files, even though
> they are no longer shipped in the linux-image package. This seems like
> it might be a violation of Debian policy, but it also seems benign.
Which part of policy are you concerned about? On its face, this seems
precisely correct.
postrm should unwind the changes which are made by maintainer scripts during
installation. It is explicitly not responsible for removing files which are
contained in the .deb: dpkg does this itself.
So if the depmod output is created in postinst, removing it in postrm is the
right thing to do.
--
- mdz