[bind10-dev] BIND bindctl review && bindctl certificate

[Shane Kerr]

Nathanael,

On Wed, 2010-03-17 at 12:51 -0400, Nathanael Hoyle wrote:
> On 3/17/2010 12:23 PM, Jeremy C. Reed wrote:
> > On Wed, 17 Mar 2010, zhanglikun wrote:
> >
> >    
> >>>   help also shows a version hardcoded in the string that should come from
> >>>   configure
> >>>        
> >> Yes, it should get the version number from configure file. (Add to
> >> TODO list) BTW, if the version number of all modules of bind10 should
> >> be same?
> >>      
> > I think all components should have their own version numbers. That way
> > if we later release a bug fix for an individual software it easy to
> > recognize. So not use the BIND 10 version number from configure.
> >
> > Do we want to reset configure.ac for every individual component version
> > change?
> >    
> 
> First posting to this list... I've been lurking for a couple of days 
> now, hope it's ok to chip in. 

It's okay - actually encouraged!
 
> Generally speaking, my preference would be to track individual versions 
> of software packages, and have them available, but to have an 
> overarching version number associated with a "bind release" that is 
> bumped whenever any of the component versions has a new version released.

I think this makes sense, so you'd get something like this:

        $ b10-auth --version
        b10-auth version 1.0.3
        BIND 10 version 10.0.0
        
Right?

--
Shane