SL Baur <steve(a)xemacs.org> writes:
We need a delete function for XEmacs packages. I can make binary
packages include a MANIFEST file that can be used by a lisp-level
delete function. Where should this MANIFEST file be placed?
a) The top level
b.1) A subdirectory
b.2) If yes to b.1, where? My suggestion is `pkginfo/MANIFEST.${PACKAGE}'
or pkginfo/${PACKAGE}
Subdirectory - pkginfo/MANIFEST.${PACKAGE} looks good.
I'm in the process of adding texinfo sources to binary package
kits. In
order to facilitate processing by the user, it would be nice to add a
generic Makefile to create hardcopy. Functionally this can work as a
template Makefile copied from the toplevel XEmacs package source
directory into the generated tarball. Is there a volunteer to create
such a Makefile? You can assume that the template will be passed the
names of the manual(s), that there is no need to worry about dependencies
of source files (they're really handled in the canonical-for-XEmacs
sources), and you can assume GNU Make is being used. Martin first asked
for this, so he is the obvious primary candidate. Any other takers?
Why not just use autoconf? For the packages as well as the info stuff?
This would remove the need for GNU make, and is similar to how everything
else works.
I've already got all the stuff built for doing various info generating
stuff in autoconf (HTML, DVI, makeinfo, info from Emacs/XEmacs).
It would not be hard to hack something together to deal with all
exisiting subdirectories when doing recursion instead of just having them
in the configure file directly.
People should be able to build packages without external dependencies,
same way they can build XEmacs with non-GNU make and compilers, etc, etc.
I'd like to see them be able to do:
cd /emacs/xemacs/package-source
./configure --with-emacs=/usr/local/bin/xemacs
make
Look familiar? :)
-Bill P.