>>>> "APA" == Adrian Aichner
<aichner(a)ecf.teradyne.com> writes:
APA> I assume it's Steve L. Baur, whose disappearance from
APA> xemacs-.*(a)xemacs.org is still a mystery to me.
Ask him. He replies to personal mail, eventually. More than that I
am unwilling to say.
APA> One field is called `standards-version'. Currently all
APA> packages in
APA> /anonymous@ftp.xemacs.org:/pub/xemacs/packages/package-index.LATEST.pgp
APA> have a 1.1 standards-version.
How about bumping this standards-version to 21.2 for all packages
known[1] to only work with (emacs-version>= 21 1)?
No. Don't overload that field. Decide what functionality is needed
in the package system, and add fields to support it.
`standards-version' will get bumped as a side-effect of this, but only
the package system should ever test that field.
APA> Then it should be fairly easy to change to PUI UI to offer
APA> the users to upgrade to the latest package of a certain
APA> standards-version. The default could be a standards-version
APA> of
APA> (string-to-number
APA> (format "%d.%d" emacs-major-version emacs-minor-version))
APA> to make things easy for the novice user.
Although rms probably will never use the package code, you might want
to put the flavor of emacs in there anyway.
Make the name of the field `required-emacs-version' or something like
that.
The main implementation difficulty with this idea is not in the pui
front end, however. It's in the back end, the archives. We need to
figure out how users with needs for older package versions can get
them.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."