Re: bug? setenv in 21.5 shadows setenv in xemacs-base
Stephen J. Turnbull writes:
>>>>> "jpw" == John Paul Wallington
<jpw(a)shootybangbang.com> writes:
jpw> The `setenv' in env.el in xemacs-base was synched
jpw> to support a SUBSTITUTE-ENV-VARS argument, and a
jpw> `substitute-env-vars' function was added to the
jpw> file. Should 21.5's lisp/process.el get the same
jpw> treatment ?
Ben has a strong argument that many of the functions in
libraries in xemacs-base should be in core. Eventually this
duplication should be eliminated. For now I would say that
if 21.5 works without those functions in core, we should
comment them out and xref env.el in 21.5's process.el. Ben
is authoritative on this, however.
The reason to keep that stuff out of the core is that you can
make more frequent releases of packages that are separate from
the core. This means bugs can be fixed immediately instead of a
year from now when the core is stable enough to be released. And
since the xemacs-base package isn't bound to any particular core
release, problems in it can be fixed across multiple releases
simultaneously. People who are still using 21.1 can get
common bugs fixed at the same time they are fixed for the stable
candidate and development branches, even though there will be no
more 21.1 releases.