João Távora <joaotavora@gmail.com> writes:
>> I think that adding this into compat.el could be also justified.
>> With compat.el being ELPA dependency.
>
> But compat.el is not :core right? So Eglot cannot depend on it.
Several packages in :core do depend on compat. The idea is to use
(require 'compat nil 'noerror), which does nothing in core, but enables
forward-compatibility features on ELPA.
Sure, that works, your right. And it's a good idea.
But it doesn't solve _this_ problem even if compat.el patches package.el, because once you get Emacs 29, you're locked out of ELPA Eglot (unless you take that very circuitous route).
> Also I think that's a bit beyond the purpose of compat, though
> I don't oppose it. I really think package.el, like other package
> managers, should learn to update itself. It should be a :core
> ELPA package itself. But then that also requires this bug to
> be fixed.
I agree that it is slightly out of scope of compat. But this particular
problem appears to be important enough as exception.
Yes, but more importantly, i don't think there's a fix to this bug that can be done fully ELPA-side.
João