Re: ITP: libsocket++ - Socket abstraction library for C++
Simon Richter <email@example.com> cum veritate scripsit:
> > Could you tell me why you are using
> > -release @RELEASE@ instead of -version 0:0:0 ?
> The regular libtool versioning scheme is only good for C libraries, i.e.
> where you can exactly tell when an interface has been added, changed or
> removed. For C++, this is difficult, since you need to take all sorts of
> compiler characteristics into account. The basic plan is to increment
> micro if the header file did not change, minor if it changed, but
> recompiling the app would still work, and major if recompiling wouldn't
> help either.
I think you are not explaining to me clearly your reasoning.
Are you saying that with every change every single package that
depends on this shared library must be recompiled ?
I have an impression that in this scheme even a change in minor
version requires a rebuild of every binary.
firstname.lastname@example.org : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org