>>>> "sc" == s champ
<junctionxyz(a)mediaone.net> writes:
sc> it'll probably be at least a few more days before a diff is
sc> submitted, to merge the new beta version of folding.el (2.93)
sc> into the text-utils package.
What's the state of this? Sorry if I missed a patch & commit.
sc> It'll take quite a few calls to
sc> #'define-obsolete-{function,variable}-alias, to make sure that
sc> the code which uses the current xemacs folding.el will work
sc> with the newer version. Should there be a seperate file,
sc> e.g.: folding-dep.el, for that?
I don't think so. It might be an idea to have a new "package
constant" file "compatibility.el" for all the obsolete symbols in the
package. But otherwise I think having a ;;; Compatibility section in
the Lisp library itself is a better idea.
sc> so the diff submitted, for the merge, would include a modified
sc> folding.el -- not the original code. Would that still be
sc> acceptable, under licensing terms?
I seem to recall maybe Steve Y answered this. But just in case: for
XEmacs it's not a licensing issue; anything that's GPL or can be
"upgraded" to GPL is fine. The important thing is for the diff to be
against the current file in CVS to make application and commiting
process smooth.
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.