Autoconf for CRM114 fun and games

I took a look back, years ago, at RPM bundling CRM114, and that work 
fell by the wayside. I've got some time now, so I've taken Joost's old 
autoconf work and wrapped the latest CRM114 release in it, partly to 
bring myself back up to speed on autoconf, and partly with an eye to 
RPMforge publishing it, and some other ideas.

It brings up a couple of things that are better questions for folks 
who've dealt with autoconf and CRM114 in the wild. Joost? If you're 
still around, I'd love your comment.

* Does *ANYONE* use the GNU regexp version of CRM114? I'd hate to bother 
building it if no one is using it and testing it.

* Is there any reason to have separate manual pages for "crm" and 
"crm114"? I can see keeping the "crm" binary name, because people's 
scripts use it. But it's easy to put in a crm.1 manpage that says ".so 
man1/crm114.1".

* This zoem tool that Joost used to generate manual pages from 
templates. It's interesting, but does not succeed on my current (Ubuntu) 
platform. Was it really that helpful? Or should I just pitch its use as 
something that was popular for a while and has fallen away, and write 
raw nroff compatible man pages for reference document generation? Or 
should we continue to *bother* with man pages, and simply dump the 
vanilla documentation in /usr/share/doc/crm114/, which is in fact the 
easiest of all?

* There ware a bunch of hooks for CVS repository integration, to 
generate release numbers, record logs, etc. The problem for me is that 
I'm not using CVS, I'm using git. git does not support '$Id$', for 
example, and for a bunch of good reasons discussed at considerable 
length in the git developer lists.  And of course my git repository does 
not have Joost's change history. In theory, I could integrate the change 
hsitory in, with a bit of work, but I'm not sure it's really needed. 
Does anyone feel attached to the use of $Id$ or CVS? Joost, if you're 
out there, if I can get you a git repository, would you consider 
migrating to it? Migration is actually pretty easy!

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com