Heiko Muenkel <muenkel(a)tnt.uni-hannover.de> writes in xemacs-beta(a)xemacs.org:
>>>>> "Hein" == P E Jareth Hein
<jareth(a)camelot.co.jp> writes:
> If you (or anyone else!) would like to be the CVS maintainer for
> a package, please send me e-mail about it, and I will set things
> up for you to be able to commit to the tree. The less work upon
> Steve, the better, eh?
Yes, I'd like to be the CVS maintainer of my packages
hm--html-menus
and view-process.
Heiko,
This was pointed out some time ago, but no resolution was reached
without feedback from you. We have a small problem with the name of
hm--html-menus. Makeinfo munges the double minus signs in the name
when it puts together the direntry. In particular, this texinfo
source from hm--html-menus.texi
@direntry
* Hm--Html-Mode:: mode for writing HTML pages
@end direntry
results in this
START-INFO-DIR-ENTRY
* Hm-Html-Mode:: mode for writing HTML pages
END-INFO-DIR-ENTRY
in the generated info file. We need either a fix for GNU texinfo that
the maintainers will accept, or we have to do something about the name
of the hm--html-menus texinfo files.
Both of the (original) packages contain also files, which are
special
for the Emacs and therefore are currently not in the CVS tree of the
XEmacs. The question is what should I do with these files?
My official policy, for whatever it's worth, is that I don't care. In
the case of something like cc-mode that is maintained separately and
where the XEmacs development team has the responsibility for consing
together the XEmacs package, the FSF Emacs files were removed[1].
Hypothetically speaking as the primary individual maintainer of
footnote and whose primary source is stored in the XEmacs CVS
repository, if there existed a footnote-fsf.el with portability stuff
for FSF Emacs, I would store it in the repository, but would arrange
to have the XEmacs build procedure not bytecompile it and either not
install it, or install it as documentation.
Should I put them also in the CVS tree and modify the Makefile, so
that I'm able to produce also a package for the Emacs with it? How
do other package maintainers handle this?
Michael Sperber does this, I believe.
Footnotes:
[1] With the consent of then-maintainer Barry Warsaw.