Hello, On Sat 23 Aug 2025 at 03:26pm -07, Xiyue Deng wrote: > The status quo means extra work from you, and I understand that you'd > like this to be fixed. On the other hand, as I mentioned in my previous > email, blocking Emacs migration due to this means that the Emacsen team > will probably need to file 3-4 RM bugs for packages like this to let > Emacs migrate each time this happens, which is also some extra efforts > that IMHO not well spent as there is no user facing issues. > > As a result, IMHO the best action to deal with this situation that saves > the most energy from everyone is probably to just remove compat-el (or > just keeping this bug open as-is). I'm CCing spwhitton and bremner to > hear their thoughts (FTR, my reason for removing compat-el can be found > in the last paragraph at [1]). > > P.S. I think compat-el is a particular package that it's more useful for > older versions of Emacs when backported, e.g. Emacs 28.2 in Bookworm > would benefit from the utilities it provides. However, IIUC, the > backporting policy requires that the package exists in testing to be a > candidate for backporting to stable, and this won't happen due to this > bug, so it's still moot. ISTM that doing the extra work to file those bugs is okay, and better than potentially having to go through NEW again. I.e., it doesn't seem to me that RMing compat-el would be a good idea. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature