[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[PATCH] dev build revision number?

From: Jani Monoses <jani_at_iv.ro>
Date: 2003-03-28 11:41:01 CET

Hi
I know this has been talked about before but I don't know if there
was a conclusion or whether is still a desired thing to have.
In order to have sometjing more meaningful than dev build in the version string
the WC number should be put there just like dist.sh does.
I put such a change in autogen.sh.
In order not to modify svn_version.h directly which would conflict at a svn up
I put the WC_VERSION in a generated file in include which is included now by svn_version
instead of the definition of SVN_VER_TAG
what do you think of this?Drawbacks or things I might have missed?

Index: autogen.sh
===================================================================
--- autogen.sh (revision 5485)
+++ autogen.sh (working copy)
@@ -65,6 +65,18 @@
 # any old aclocal.m4 left over from prior build so it doesn't cause errors.
 rm -f aclocal.m4
 
+#Create wc_version.h containing WC number
+
+### Estimated current version of your working copy
+echo "Creating wc_version.h"
+
+WC_VERSION=`svn st -vN doc/README | awk '{print $1}'`
+cat >subversion/include/wc_version.h <<piggy
+/* Automatically generated at build time.Contains the WC version this build is based on */
+#define SVN_VER_TAG "dev build of r$WC_VERSION"
+piggy
+touch subversion/include/svn_version.h
+
+
 # Produce getdate.c from getdate.y.
 # Again, this means that "developers" who run autogen.sh need either
 # yacc or bison -- but not people who compile sourceballs, since `make

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 28 11:36:49 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.