Steve Youngs <sryoungs(a)bigpond.net.au> writes:
1) Move the stuff in fsf-compat that isn't purely a
compatibility
layer to other packages.
2) Fix any package that depends on fsf-compat.
3) Deprecate fsf-compat.
Agreed 100%. fsf-compat started out as a compatibility layer for
broken FSF code that our *users* want to run. It was never meant to
be a legitimate API for our own use.
(It doesn't mean that all FSF's APIs are forbidden in XEmacs; it is
perfectly fine to adopt their design into XEmacs. But the
compatibility layer should remain exactly that.)