Jan-Ãke Larsson <[EMAIL PROTECTED]> writes: > David Kastrup wrote: >> a) take the version string from autoconf. > > This is the usual way to do it. > >> e) Just go by the last ChangeLog entry (releases have special syntax >> and can be discerned). > > Since we have quite a few CVS users, I can see the need for doing it > this way. > >> d) use the release number if a regularly exported release, use the >> topmost date in the ChangeLog file if not. > > This is probably the sanest alternative. Now, ISTR Uwe is using his > own CVS repository for XEmacs packaging, correct? This has to be > robust so that we won't get confusing bug reports, for Uwe's XEmacs > packages.
I see no problem here. You have to export using a particular release tag in order to get the release string, and I doubt that XEmacs developers do that with a release version string compatible to ours. I also have been unable to persuade Uwe to use the "cvs admin -kb" option on tex.el so that their CVS does not tamper with our version numbers, so I think that this will likely continue when we move the version $Name: $ string into auctex.el. So the version would revert to the ChangeLog date always and never to an upstream release number. Which is probably not the worst idea. Given the recent fallout on the XEmacs beta development lists where it was quite categorically stated that if we provided completely finished packages for XEmacs ourselves, they would not get used anyway, it might be an idea, once that the build process is valid for the whole AUCTeX package, to provide XEmacs packages of our own and ask the XEmacs maintainers to change the bug reporting address of their own variant. I don't really fancy dealing with bug reports for a version for which we are considered irresponsible. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ auctex-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/auctex-devel
