Well, I don't see a problem in having to add features to OpenBSD m4 to stay
in synch with what autoconf needs from gnu-m4.
As long as those features are not gratuitous, and just put there to annoy
me and make sure autoconf only works with gnu-m4, I won't complain too
much :)
I'll admit to not having the --trace stuff in OpenBSD m4 yet, since I've
tested everything with autoconf 2.13 up until now (wanted to make the latest
stable work. I would have worked with autoconf 2.14 if that specific beast
had made it into a release (hint, hint: how comes you make such infrequent
releases ? I know about the synch issues with other related projects like
automake, but really, sometimes you just need to ship a project out the
door, works wonder with motivating sister projects to do some work...) ),
but this is probably reasonably easy...
I'm also reasonably savvy about changing small details (e.g., replace gm4
with m4 -g in the autoconf shell-scripts, or fixing temp files security
holes...) to get autoconf to run.
Specifically, finding incompatibilities in autoconf/OpenBSD m4 is my turf,
I won't ask you to check for that, and I'll even fix them by myself.
I'll just argue if I feel the FSF is picking on us... :)
--
Marc Espie
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don't die, they just get out of beta'
