Hi Sean, Sean Whitton <spwhit...@spwhitton.name> writes:
> Hello, > > On Sat 24 May 2025 at 04:37am -07, Xiyue Deng wrote: > >> This sounds interesting. I think another possible fix is to let >> emacsen-common do `emacs-remove $FLAVOR' on preinst, so that the elpa >> directory of the old version of addon is cleaned up; and `emacs-install >> $FLAVOR' on postinst to handle the current version of the addon (could >> be old if the newer version is not yet unpacked). This requires that an >> addon is not configured/set-up before emacsen-common, which seems to be >> the case during my testing because an addon Depends on emacsen-common, I >> guess. Would be good if someone can confirm this behavior from from >> `apt upgrade'. > > We don't need to do this by experimentation :) > > Everything about what maintscripts may and may not assume is written > down in Policy. Please take another look. > Indeed. Policy seems to confirm the assumptions this solution requires. I have implemented this in this RM[1], and run in my docker instance several times to test it and it seems working. Please review. [1] https://salsa.debian.org/rlb/deb-emacsen-common/-/merge_requests/3 > -- > Sean Whitton -- Regards, Xiyue Deng
signature.asc
Description: PGP signature
