[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: versioned libraries dependencies

On Tue, Nov 19, 2002 at 10:55:20PM +0100, Stefano Zacchiroli wrote:
> On Tue, Nov 19, 2002 at 09:59:11PM +0100, J?r?me Marant wrote:
> >   Yes I understood correctly. But it is not necessary to make it mandatory
> >   since it really depends on applications. Those which are source compatible
> >   won't require it.
> Yes, it is necessary to make it mandatory.
> If you have a library libA-ocaml-dev which build depends on
> libB-ocaml-dev _AND_ (but please not that this is the usual case)
> libB-ocaml-dev needs to be linked in each time you develop using
> libA-ocamld-dev then you have to rebuild libA each time you rebuilt
> libB, otherwise the linking against both this library will be
> impossible.

Each time you rebuild in an incompatible way ?

I don't have time to explore this in detail, but i maintain lablgtk and
lablgl, which correspond exactly to the above description, and i use
them together in my own program.

I remember having upgraded lablgtk and lablgl separatedly and it
continued working.

your point is that i cannot rebuild lablgl without having to rebuild
lablgtk, isn't it ? I will check that. 

Mmm, i built lablgl 0.98-1 on Wed 21 august and just after that i built
lablgtk 1.2.5-1.

Then i modified lablgtk and rebuilt it in -2 and -3 without changing
lablgl, and it continued to work.

Then i rebuild lablgl 0.98-2 and lablgtk 1.2.5-4 together.

But it is the opposite idea you re worrying about. I will thus rebuild
lablgl, install it and see what happens.

... some building, installing and building.

Ok, i installed 0.98-3, and rebuilt my tool, configured it to use openGL
instead of Gdk, and ran it, no problem.

That said, i did only change a thing in the debian/rules (having a
lablGL symlink to lablgl), so this will be the exact same code.

Also, from my experience, not all code change will cause the
icncompatibility message, only those that change the .cmi, right ?

So it would be mandatory to bump the version only if the .cmi do change.
Ideally, we would have a tool which checks that.


Sven Luther

Reply to: