Hey Pau, 2010/7/23 Pau Garcia i Quiles <[email protected]>: >> I believe we had a discussion about this a few months ago, and then we >> concluded that whenever one library gets bumped, all dependent >> libraries should be bumped too. And then we can just as well bump them >> all to the same version. A soversion is just an integer, and so by >> "more correct" you mean that bumping all to the same number is bit >> onorthodox (just this once) and next time we will be "very correct" ? > > Sorry for the delay in answering. > > We discussed a related issue on (fake) IRC and private e-mails at the > end of March. > > Back then, what we talked about was bumping soversion on dependent > libraries when dependee libraries were bumped. I. e. if you make > ABI-incompatible changes to libwt, you need to bump libwt soversion > and therefore, you need to bump libwthttp, libwtfcgi, etc.
That's it. > But here is the catch (we did not talk about this): just not > necessarily bump all soversions to the very same soversion! In fact, > usually you do not want to have the same soversion for all libraries. Okay, I understand what I did wrong and why it is wrong :-) > So my advice is: > > 1) When you make binary-incompatible changes, bump soversion for > that library and all its dependent libraries. I. e. if you made > ABI-incompatible changes to libwt, you need to bump libwthttp, > libwtfcgi, etc (everything) > > 2) Do not bump soversion unless it is needed. I. e. if you made > changes to libwtdbo but you did not make changes to any other library, > bump only libwtdbo* but do not bump the soversion of libwt, > libwtisapi, libwthttp, libwtfcgi and libwtext and libwtext > > 3) Do not use the same soversion for all libraries. The moment you > hit case 2 above, you'll realize it does not make sense to have the > very same soversion for all libraries. In fact, if you were to use the > same soversion number, why bother having 8 different variables? :-) I get it now, thanks ! Regards, koen ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
