On Fri, Aug 06, 2010 at 07:39:49AM +0200, Ralf Wildenhues wrote:
> * Jack Howarth wrote on Fri, Aug 06, 2010 at 02:31:31AM CEST:
> > I have been mulling over how to transition the
> > current gcc4x and cloog packages in fink to the new
> > ppl-0.11 release and believe we really need to have
> > a soversion bump on cloog to safely do this on
> > systems with pre-existing packages.
>
> Not sure I understand, but why should ppl soversion bump require a cloog
> soversion bump? In which way is this different from any other library
> dependency that undergoes such a bump, and why should it be handled
> differently?
>
> Thanks,
> Ralf
Ralf,
My point was that in this case not only does ppl-0.11 require
the existing soversion of cloog to be rebuilt but also all other
previously built gcc releases that used it as well.
Considering that the existing cloog-0.15.9 sources refuse
to build against ppl-0.11 due to the version check, it presents
an opportunity to do a soversion bump and a cloog-0.16 release
which would require ppl-0.11 as the minimum required ppl. I do
understand that this isn't the conventional reason to do a
soversion bump, but it does have the advantage of solving the
coherency problems in gcc/cloog/ppl builds.
Jack
