Ville Skyttä <ville.skytta(a)xemacs.org> writes:
> Ok, I have committed a SASL package in unsupported/simon/sasl/
now,
> and updated the ECRYPTO package in unsupported/simon/ecrypto/ which
> contains some files that SASL needs. ECRYPTO includes md5, which
> might not be needed, how far back in XEmacs versions are packages
> supposed to support? MD5 has been core functionality for quite a
> while. It shouldn't be harmful though, so I think it is safest to
> leave it in, unless someone has another opinion. Gnus and W3 packages
> also includes md5.el, btw.
ISTR somebody talked something about licensing issues with ecrypto (the
IDEA code)? If this was the case and/or if it can be left out, let's
leave it.
Ah, yes, IDEA is patented in some countries (but not all). I'd
distribute it and fight the IDEA people in court, but I guess they
won't be suing me if XEmacs distribute it, so I removed it to save
someone else from the trouble. If someone responsible is willing to
fight them in court, I think it would make a nice statement to include
it though.
AFAIK, XEmacs packages should work with 21.1 and newer.
OK. md5 is needed then.
> Moving the directories into xemacs-packages/ and updating
Makefile and
> package-info.in should be enough. Wha'd'ya say? I have even done
> some minimal testing, so it might even work.
Nice:) I mailed about docbookide, ocaml and sml-mode earlier today,
let's move sasl in the same batch with them. I suppose a repository
move would be the way to do it this time...
Yup.