On Fri, 2012-02-17 at 15:59 +0000, Manuel A. Fernandez Montecelo wrote: > 2012/2/17 Sam Morris <s...@robots.org.uk>: > > After installing the 1.7.4-1 debs, I was left with: > > /etc/OGRE-1.7.3 (empty directory) > > /etc/OGRE/plugins.cfg.dpkg-remove > > [...] > > Without a dummy libogre-1.7.3 package that would exist solely to call > > rm_conffile in its postinst, perhaps we could solve this by having > > libogre-1.7.3's postinst script run rm > > -f /etc/OGRE/plugins.cfg.dpkg-remove... if the file doesn't exist then > > there is no side effect, and if it does then the user would already have > > had to remove libogre-1.7.3 because libogre-1.7.4 conflicts with it. > > OK. But I guess that /etc/OGRE-1.7.3 should be removed as well, if it's > empty?
Oh yeah, I forgot to suggest that! :) > Thank you very much for your help again. > > Cheers. You're welcome! Let me know if you want me to test anything else--I've still got my build server that had my locally modified package installed. I see you're using the ~ trick when invoking rm_conffiles now so I can either test the package in git to see what happens, or wait to test that + the final removal of libogre-1.3.7's config file. Regards, -- Sam Morris <s...@robots.org.uk> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
