[Libvisual-devel] about versioning system

[Duilio J. P. <dp...@fc...>]

Dennis wrote on another thread:
> Maybe it's better to use #defines for setting version anyway, so we have
> more control regarding that, I'd like to do a 0.2.0 to sign it's 
> significancy, and because it will be major API incompatible.
> 
> > Other possibility would be to introduce libtool versioning right now,
> > but I think is not the moment yet. Remember the current:revision:age
> > scheme of libtool (which is reflected on the package number). 'current'
> > must be incremented every time you change an actual API function, and
> > that will happen for a while on libvisual, so we will have
> > libvisual-10.0.4 really soon :-)
> 
> Maybe we should use a different versioning scheme after all... not sure

Of course versioning system could be controlled during configure time, 
through pkg-config. In fact there are so many things in common between
libtool and pkg-config objectives, that libtool project's people are
thinking about 'merge' the two projects someway.
Anyway, we can control versions entirely through pkg-config, we just
must very strict about this on any new release (specially when some day
became projects using libvisual outside our own).


Bye,
Duilio.