On Fri, Jan 04, 2013 at 03:56:54PM -0500, Rafael Schloming wrote: > > Not difficult, no. We just have to pass it through a similar filter as > > would be done when using autoconf. For development purposes the version > > doesn't matter, just when we're creating those artifacts. > > > > So we could change release.sh to take the version number that's passed > > in and use it, though that's duplicating what's in the root > > CMakeLists.txt already. It just needs to be something we don't have to > > pass into the build system for packaging, for example. > > > > I think if we were to consolidate it into one place we'd pick a file in svn > and have both release.sh and CMakeLists.txt pull it out of there and nix > the release.sh parameter. That way the svn number encoded in the release > will always point to a source tree that builds with the correct version.
+1 That sounds good to me. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgpDAFGk8AqyB.pgp
Description: PGP signature
