Strategy to specify major, minor, and patch versions

What's the best way to set up an autoconf project so that the major, minor and patch version numbers are made available to the entire package (automake and source code) and used to define the VERSION and PACKAGE_VERSION variables? Thanks, Zé ___ Au

Re: Strategy to specify major, minor, and patch versions

On 08/27/2014 03:52 AM, Zé wrote: > What's the best way to set up an autoconf project so that the major, > minor and patch version numbers are made available to the entire package > (automake and source code) and used to define the VERSION and > PACKAGE_VERSION variables? Here's how libvirt does i

Re: Strategy to specify major, minor, and patch versions

On 08/27/2014 07:52 PM, Zé wrote: What's the best way to set up an autoconf project so that the major, minor and patch version numbers are made available to the entire package (automake and source code) and used to define the VERSION and PACKAGE_VERSION variables? I use this macro in my proje