Re: versioned libraries dependencies
Stefano Zacchiroli wrote:
On Wed, Nov 20, 2002 at 08:58:52AM +0100, J?r?me Marant wrote:
Do you hav a concrete example? It looks like a problem with applications
Just try to build an application that use both netclient and netstring
in current unstable.
Do you have such an application tha I can try?
This is _not_ a problem with shared objects, this is a problem related
to the way ocaml ensure that type information are correct.
Each ocaml library keeps a table of md5sums of all .cmi against it was
built, if you try to use a .cmi with the same name but with a different
md5sum ocaml compiler will fail.
When does a md5sum change?
Please not Jerome that this is not a problem to be discussed here, this
is how ocaml compiler work.
Hey, you seem to be annoyed with me trying to understand the problem :-)
As I said in previous mails, I won't block anything as long as it makes
sense to me.
Here we have to discuss which is the better why for debian to live with
this compiler (bug?)feature. IMO the best way is using versioned
dependencies between libraries so that a DD doesn't forget to rebuild
all libraries which depend on the one he is rebuilding.
But the problem occurs only when you want to rebuild an application, right?