Comment by ~minifridge on ~pkal/compat
Yes, you are right. None of the packages failing actually use the
compat-declare-versionmacro. They just depend oncompat
"~minifridge" outgoing@sr.ht writes:
packages that use
compat-declare-versionbreak under compat 28.1.2.compat-declare-versionis defined as a macro and other functions do not perform macro-expand. Defining this macro definition as a function is a work around.No package should use
compat-declare-version, that is an internal macro defined incompat-macs.el, so I am afraid I don't understand the issue.What exactly breaks? Also, are you using an atypical package management system (straight, borg, ...)?
Ticket created by ~minifridge on ~pkal/compat
packages that use
compat-declare-versionbreak under compat 28.1.2.compat-declare-versionis defined as a macro and other functions do not perform macro-expand. Defining this macro definition as a function is a work around.