-You must fill in the four commented lines. The value of @code{name} is
-the name of your package as an unquoted symbol. Normally it is the name
-of the main Lisp file or principal feature provided. The allowed values
-for distribution are @code{xemacs} and @code{mule}. Write them as
-unquoted symbols. The @code{description} is a quoted Lisp string; use
-the usual conventions. The value for @code{provides} is a list of
-feature symbols (written unquoted). All of the features provided by
-libraries in your package should be elements of this list. Implementing
-an automatic method for generating the @file{provides} line is
-desirable, but as yet undone.
-
-The variables in upper-case are references to variables set in the
-@file{Makefile} or automatically generated. Do not change them; they
-are automatically filled in by the build process.
-
-The remaining lines refer to implementation constants
-(@code{standards-version}), or features that are unimplemented or have
-been removed (@code{priority} and @code{dump}). The @code{type} line is
-not normally relevant to external maintainers; the alternate value is
-@code{single-file}, which refers to packages consed up out of a number
-of single-file libraries that are more or less thematically related. An
-example is @code{prog-modes}. Single-file packages are basically for
-administrative convenience, and new packages should generally be created
-as regular packages.
-
-The @file{Makefile} is quite stylized. The idea is similar to an
-@file{Imakefile} or an @code{automake} file: the complexity is hidden in
-generic rules files, in this case the @file{XEmacs.rules} include file
-in the top directory of the packages hierarchy. Although a number of
-facilities are available for complex libraries, most simple packages'
-@file{Makefile}s contain a copyright notice, a few variable definitions,
-an include for @file{XEmacs.rules}, and a couple of standard targets.
-
-The first few @code{make} variables defined are @code{VERSION},
-@code{AUTHOR_VERSION}, @code{MAINTAINER}, @code{PACKAGE},
-@code{PKG_TYPE}, @code{REQUIRES}, and @code{CATEGORY}. All but one were
-described in the description of @file{package-info.in}. The last is an
-admistrative grouping. Current categories include @code{comm},
-@code{games}, @code{libs}, @code{mule}, @code{oa}, @code{os},
-@code{prog}, and @code{wp}. @ref{Available Packages}, for a list of
-categories.
-
-Next, define the variable @code{ELCS}. This contains the list of the
-byte-compiled Lisp files used by the package. These files and their
-@file{.el} versions will be included in the binary package. If there
-are other files (such as extra Lisp sources or an upstream
-@file{Makefile}) that are normally placed in the installed Lisp
-directory, but not byte-compiled, they can be listed as the value of
-@code{EXTRA_SOURCES}.
-
-The include is simply
-@example
-include ../../XEmacs.rules
-@end example