Adrian Aichner <aichner(a)ecf.teradyne.com> writes:
>> before Yoshiki's patch. The new feature of
>> `completing-read', the DEFAULT argument, cannot be relied
>> upon (because XEmacs-21.1.8 does not have it).
Hrvoje> Sorry, I don't agree with "cannot be relied upon" part.
Hrvoje> Backward compatibility is a nice thing, but can't we
Hrvoje> just have the new version of the package support the new
Hrvoje> XEmacs?
Forcing people who have and latest released and the latest beta
XEmacs installed to maintain two separate XEmacs packages trees
manually? Shudder!
Why the shudder? It used to be normal that a novel API caused update
of the actively maintained packages. The people with older Emacsen
just used the older versions of packages.
The package system apparently made this harder, not easier.
I agree. Packages were separates from XEmacs to ease their
evolution, right? Having them tied to a particular XEmacs is bad.
Tying them to an API version (of core lisp functionality) might be
feasible.
Is the standards-version field of the `package-get-base''s plist
intended to be used to track API changes?
I don't know. :-(
Does our package system really have an active maintainer at this
point? Michael, come to the rescue!