The packages in this directory contain full sources *for each package
as installed*.  To modify package code in-place,

1. Determine the library containing the function you wish to change.
2. Use M-x find-library to read the code into a buffer, and edit it.
3. Repeat as necessary.
4. If you have added any autoload cookies or changed any autoloaded
   functions, use M-x update-file-autoloads.
5. Run M-x byte-recompile-directory to recompile all .elcs whose
   corresponding .els have changed.

A similar procedure can be used for modifying Texinfo documentation
(the sources with be in a subdirectory named for the package in the
man directory which is the "uncle" of the directory containing Lisp
code).  Rebuild the Info files with makeinfo.

Of course you can generate patches to send to XEmacs for inclusion in
future versions.  You must preserve the original file somehow, of
course.

More convenient for developers and redistributors is the package
source repository in XEmacs CVS.  See http://cvs.xemacs.org/ for more
information.  If you are an experienced CVS user, then login to the
anonymous pserver with password "cvs", then checkout the packages module.

cvs -d :pserver:cvs@cvs.xemacs.org:/pack/xemacscvs login
cvs -d :pserver:cvs@cvs.xemacs.org:/pack/xemacscvs checkout packages

CVS provides file history, of course, and allows you to generate
patches against the current developer sources without worrying about
keeping backups of the current version.  The version of the package in
CVS also provides support for building binary-with-source packages, as
provided in this directory.  Sorry, we do not provide prebuilt
binaries or tarballs of the CVS sources.