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

Re: Ocaml 3.08.0-2 ready to enter testing, hold back by 54+4 packages.



On Fri, Aug 06, 2004 at 09:37:18AM -0500, John Goerzen wrote:
> On Fri, Aug 06, 2004 at 04:35:26PM +0200, Sven Luther wrote:
> > On Fri, Aug 06, 2004 at 08:55:34AM -0500, John Goerzen wrote:
> > > I have no reasno to believe that ounit will be incompatible with OCaml
> > > 3.09.  In fact, it works fine with 3.07 too.  If somebody has that
> > 
> > Ocaml upstream strongly recomends to rebuild each time there is a new upstream
> > compiler release. This is why they now also have the stable and the
> 
> I am not disputing that (any more).  The ounit *SOURCE* will be
> compatible.

Well, sure, but in the current state of affairs, the ounit source *PACKAGE*
will not be compatible. You are free to propose a scheme and discuss this here
for the next ocaml compiler release, but this is a sarge+1 issue. For sarge we
will go with what is proven to work.


> > > Perhaps we can use the shlibs mechanism or something for this?
> > 
> > Yes, that would be nice, still we have trouble in case of you uploading iounit
> > a day or two before i upload a new ocaml, and then it is well possible that
> > the different arches will have a iounit built with a different ocaml.
> 
> True; however, the dependencies will still be correct and prevent a
> castrophe.

Ok, but right.

> > > > > ounit will enter testing as soon as the s390 build is uploaded and its 
> > > > > 10 days are over, because its dependency on ocaml will be satisfied in 
> > > > > testing). I can file a serious bug in the BTS if necessary, to block 
> > > > > this migration.
> > > 
> > > What exactly is the problem with this?
> > 
> > It is not policy compliant.
> 
> In what way?

Well, i have to check, but the idea is to mandate the explicit build-depends
on ocaml-3.08.

Anyway, like said, i would be happy to rediscuss this later on, when sarge is
released, and that we find the time to get the shlibs mechanism to fill the
dependencies automatically and also have some automated way to find the ocaml
versioned directory (needs some substvar handling in .dirs and .files mostly,
ocamlc -where should give the right thing), but this is a post sarge issue.

Friendly,

Sven Luther



Reply to: