Simon Josefsson <sj(a)extundo.com> writes:
It raise a sort-of fundamental problems, should XEmacs custom.el
It doesn't really sense in XEmacs context, because most Lisp files are
part of packages that are mostly independent of the XEmacs version.
(I don't know in what way Emacs actually use the field.)
There is a "customize-changed-options" command which prompt for an
EMacs version, and create a customize buffer with all the options with
a :version tag that indicate the option is more recent than that.
If XEmacs custom.el don't support :version (which is the current
case), do you think it's good to include :version fields in FSF synced
files in XEmacs just for sake of minimizing differences? I'd like to
do that, but I guess it could cause problems if XEmacs at some point
changed their mind about supporting :version.
I think XEmacs should just ignore :version, and don't bother removing
it from "synched" packages.