[Nut-upsuser] Belkin F6C1100-UNV

[Eric S. Raymond]

Peter Selinger <selinger at mathstat.dal.ca>:
> I am in favor of this. I have wanted this for some time, but was not
> sure how best to do it. 
> 
> We also have to have a way to suppress the revision-stamp mechanism in
> an actual distribution. In other words, SVN builds should have a
> version number such as 2.1.0-r910, whereas builds from released
> tarballs should have a proper version number such as 2.0.6. 
> 
> It would be best to include a boolean flag at the top of configure.in,
> just after the AC_INIT version number, so that a maintainer who
> generates a distribution will not forget to disable the revision-stamp
> mechanism. What I have in mind is something like:
> 
> AC_INIT(nut, 2.1.0)            dnl Update this number to make a release
> INCLUDE_SVN_REVISION=yes       dnl Change to "no" to make a release
> 
> and then change the call to AC_DEFINE_UNQUOTED(UPS_VERSION, ...) later
> in configure.in.
> 
> Question: should this only work if the user re-runs ./configure after
> an update, or should it work at the Makefile level? 

The way I implemented this was by adding an --enable-display-revision 
switch to Battle For Wesnoth's configure.ac.  What you can do is change
the switch default -- on for point releases, off for official ones.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>