Need help with package maintenance

Hi all Scratching an itch with mmm-mode, I found that the MMM package is in need of some love. Better, I found that the latest version of MMM (from 2004, BTW.) fixes the issue I am having. Between our current version of MMM (0.4.7, 2001 A.D.) and the current (0.4.8), there have been some changes in upstream file organization. The current state of my work is that everything compiles with my XEmacs 21.5.b28 and works as expected. In particular that bug is gone! I split the ChangeLog into an upstream version and an XEmacs version to track changes separately. My questions are regarding packaging. Current MMM uses autoconf with all these additional files. We're not really using any of these. Which of these go into our CVS? Do we have to ship these files with the compiled package for legal reasons? What about pre-generated info files? These are really just courtesy copies so I suppose we don't have to check them in. Here is the list of files I am not sure what to do with: Unknown INSTALL Unknown Makefile.am Unknown Makefile.in Unknown acinclude.m4 Unknown aclocal.m4 Unknown configure Unknown configure.in Unknown elisp-comp Unknown install-sh Unknown mdate-sh Unknown missing Unknown mkinstalldirs Unknown stamp-vti Any ideas? How shall we proceed? Thanks Marcus -- note that "property" can also be used as syntaxtic sugar to reference a property, breaking the clean design of verilog; [...] (seen on http://www.veripool.com/verilog-mode_news.html) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta