Hi Sean, Sean Whitton <spwhit...@spwhitton.name> writes:
> Hello, > > On Fri 23 May 2025 at 01:40pm -07, Xiyue Deng wrote: > >> I don't know whether there is another way to ensure that an addon is >> not unpacked when emacsen-common is also unpacked but not >> configured/set-up. Pre-Depends on emacsen-common ensures this. > > There might not be, but it might be possible to fix this concrete > problem without ensuring that an addon is not unpacked when > emacsen-common is not configured. > 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'. This basically does what emacsVAR does during `apt dist-upgrade', which circumvents this issue during my testing. If this process sounds about right, I can try to implement and test. > -- > Sean Whitton -- Regards, Xiyue Deng
signature.asc
Description: PGP signature
