On Thu, Apr 10, 2014 at 05:50:15PM +0200, Andreas Beckmann wrote:
> On 2014-04-10 17:40, Agustin Martin wrote:
> > However, postrm cannot rely on anything in dependencies, there is no
> > warranty on removal ordering. So, script is not available and not run if
> > dictionaries-common is removed first (which can happen) and those dirs are
> > left behind. This is something I am trying to fix in new -dev debhelper
> > snippets allowing for explicit removal of those dirs if empty.
> 
> can't you do this cleanup already from somedict.postrm remove (instead
> of somedict.postrm purge)? 

It is already done at postrm removal stage. However, I now notice that when
the removal script in first snippet is run, even if there is a single
installed dict, /var/lib/{a,i}spell still has some contents that will be
removed later by the second snippet, and thus the dir is not removed. I have
to think about reversing debhelper snippets ordering.

> During removal the dependencies are all
> satisfied (including the package owning the directory), only at purge
> time they are not. 

Note that unless something has been changed recently, this may not be true.
See message http://bugs.debian.org/504880#106, from Ian Jackson. One should
better not rely on dependencies being installed at postrm.

Regards,

-- 
Agustin


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to