Richard Lewis <richard.lewis.deb...@googlemail.com> writes: > the latter - new emacsen-common is present but in state 'unpacked' before > new dh-* is unpackaged
I think I may understand what's going on now, and if so, the issue rests on a misunderstanding in emacsen-common about how the maintainerscript states work. We've been discussing some improvements, some more dramatic than others on #debian-emacs, and I've been toying with some of the possibilities. > ( i suspect dpkg triggers should be the answer- should the question be > understood better --- eg it looks like jed does something similar with .sl > files, at least i think it does -- i didnt find any documentation on that > either) Hah, that's one of the approaches I've been toying with for the past few days. If it pans out, I'll likely make a proposal along with changes to debian-emacs-policy in a while. I'd considered triggers a few times in the past, but only recently thought of a way that addresses the issues I'd previously been concerned about. If this does work out, we're also likely to add recompilation of rdepends during add-on package upgrades (i.e. in case "public" macros have changed in incompatible ways). Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
