Is there a reason for an Emacs package not to be included in XEmacs?
The reason for an Emacs package not to be included in XEmacs is usually one or more of the following: • The package has not been ported to XEmacs. This will typically happen when it uses GNU-Emacs-specific features, which make it fail under XEmacs. Porting a package to XEmacs can range from a trivial amount of change to a partial or full rewrite. Fortunately, the authors of modern packages usually choose to support both Emacsen themselves. • The package has been decided not to be appropriate for XEmacs. It may have an equivalent or better replacement within XEmacs, in which case the developers may choose not to burden themselves with supporting an additional package. Each package bundled with XEmacs means more work for the maintainers, whether they want it or not. If you are ready to take over the maintenance responsibilities for the package you port, be sure to say so–we will more likely include it. • The package simply hasn’t been noted by the XEmacs development. If that’s the case,
