Le lundi 13 septembre 2010 05:51:15, Reinhard Tartler a écrit :
> On Fr, Sep 10, 2010 at 23:02:05 (CEST), Romain Beauxis wrote:
> >       Hi all,
> > 
> > I just realized that the binNMU of libbjack-ocaml(-dev) was not
> > sufficient  because libbjack-ocaml-dev declares a dependency on
> > libjack-dev.
> Sorry? I don't follow. can you please elaborate why this doesn't work?

Sorry, I should have been more precise..

> > I think it is reasonable to have a dependency on the -dev package of a
> > library  when installing the corresponding ocaml -dev binding, so I want
> > to know what to do now.
> Do the ocaml jack bindings work with both jackd1 and jackd2? or do they
> require a specific flavor? what about potential other jack
> implementations like tschack?

The bindings do not require any particular flavor. The problem is that any 
program using libbjack-ocaml must compile against it, thus installing 

libbjack-ocaml-dev has a dependency on libjack-dev, which pulls jackd1. I 
believe that instead one should be able to use any jack implementation for the 

Also, when building liquidsoap inexperimental, I have a failure in cowbuilder 
because some of the dependencies pull jack2 and ocaml-bjack pulls jack1.

Adding a dependency on the developpement package of the corresponding C 
library in libbjack-ocaml-dev seems a reasonable requirement to me, though I 
think it has been discussed in that past I think.

The straight-forward solution would be to change this dependency to 
  libjack-jackd2-dev | libjack-dev
but I would like to know if this is the solution you would advise.

Then, the other questions is: should this be also propagated to testing ? The 
answer seems to be yes to me but again, I would like to have your input on 


pkg-multimedia-maintainers mailing list

Reply via email to