OK for me
by "Same for carob friends", what do mean ? a compatibility table vs.
carob ?
For next carob build, I think it will be a 1.0, as the API changed since
0.5 (from what I remember, at least connection parameters, probably
others like setNull)
Csaba, do you need one (a new carob build) ? because I am a bit
reluctant calling carob "1.0" (regarding its current state, ie. more a
beta than a release)
Csaba Simon a écrit :
Nice idea.
Let's sum what we have:
* carob numbering will reflect the "exported" interface with major and
minor numbers (carob-1.0, carob-1.1, carob-2.0...) If we break the ABI
compatibility we increase the major number. Carob version and the
libcarob.so.x.y version will be the same.
* "version compatibility table" (copyright Gilles) on carob's web page
What we need to do:
* in the Makefile the LIB_MINOR_VERSION is missing
* -version-info LIB_MAJOR_VERSION:LIB_MINOR_VERSION linker switch when
producing the libcarob.so.x.y library
* in the README point to the version compatibility table web page
In this way the carob libraries can happily coexist on the same system
(/usr/lib/libcarob.so.1.0, /usr/lib/libcarob.so.2.1 ...)
The only problem remains with the header files. But this is a
packaging problem. I think if we can use for the headers separate
directories than we are done. Example: /usr/include/carob-1.2/,
/usr/include/carob-2.0/
Same for Carob friends.
Is this OK?
Regards,
Csaba
_______________________________________________
Carob mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/carob
_______________________________________________
Carob mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/carob
