On Tue, Oct 08, 2013 at 08:17:09PM +0200, Pieter Hintjens wrote: > Do all libraries do this? it goes directly against the advice of that > page I quoted.
Most libraries do *not* do this. New functionality does not break ABI compatibility according to everything I've seen and read. SONAME does only give you compatibility with old apps and new libraries, not new apps and old libraries. The implicit assumption is that the latest version of the library is used everywhere, since there's no recompile of apps necessary to use it. > On Tue, Oct 8, 2013 at 7:07 PM, Jose Pedro Oliveira <[email protected]> wrote: > > > > On 2013/10/08 17:28 , Pieter Hintjens wrote: > >> On Tue, Oct 8, 2013 at 6:18 PM, Jose Pedro Oliveira <[email protected]> > >> wrote: > >> > >>> And what happens if I have an application that uses the v4 new features > >>> and I copy it to a system where there is only ZeroMQ v3 installed? > >> Well, it won't work, for sure. > >> > >>> Note that ldd only reports the requirements based on the major number > >>> (and yum/rpm also have a similar behaviour): > >> That seems unfortunate and contradictory to the libtool rules. I'm > >> sure there's a rationale but I don't know it. > >> > >> What is your suggestion? Afaics simply incrementing the major ABI > >> number at every stable release is not feasible (4.1. 4.2, ...) > >> > > Suggestion: Bump only at the major stable releases (e.g. from v3 to v4). > > > > Currently in Fedora/EPEL we are supporting parallel installation of > > of ZeroMQ v2 (2.2.0) and ZeroMQ v3 (3.2.4) libraries; and > > we are also interested in supporting the parallel installation > > of the ZeroMQ v4 libraries. > > > > Current package contents in Fedora: > > ---------- > > # rpm -ql zeromq > > /usr/lib64/libzmq.so.1 > > /usr/lib64/libzmq.so.1.0.1 > > /usr/share/doc/zeromq-2.2.0 > > /usr/share/doc/zeromq-2.2.0/AUTHORS > > /usr/share/doc/zeromq-2.2.0/COPYING > > /usr/share/doc/zeromq-2.2.0/COPYING.LESSER > > /usr/share/doc/zeromq-2.2.0/ChangeLog > > /usr/share/doc/zeromq-2.2.0/NEWS > > /usr/share/doc/zeromq-2.2.0/README > > > > # rpm -ql zeromq3 > > /usr/lib64/libzmq.so.3 > > /usr/lib64/libzmq.so.3.0.0 > > /usr/share/doc/zeromq3-3.2.4 > > /usr/share/doc/zeromq3-3.2.4/AUTHORS > > /usr/share/doc/zeromq3-3.2.4/COPYING > > /usr/share/doc/zeromq3-3.2.4/COPYING.LESSER > > /usr/share/doc/zeromq3-3.2.4/ChangeLog > > /usr/share/doc/zeromq3-3.2.4/NEWS > > /usr/share/doc/zeromq3-3.2.4/README > > ----------- > > > > Note: > > * you can't parallel install the zeromq[n]-devel packages > > (will cause file conflicts; e.g. libzmq.so) > > > > > > Regards, > > jpo > > -- > > Jose Pedro Oliveira > > * [email protected] * > > > > _______________________________________________ > > zeromq-dev mailing list > > [email protected] > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev -- AJ Lewis Software Engineer Quantum Corporation Work: 651 688-4346 email: [email protected] ---------------------------------------------------------------------- The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt. _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
