[Pkg-scicomp-devel] suitesparse build-depends on libparmetis-dev => FTBFS on several buildds

[Daniel Rus]

2007/5/31, Christophe Prud'homme <prudhomm at debian.org>:
> Daniel,
>
> I reverted for the moment the -metis package and uploaded 3.0.0-3
>
> [snip]
> | A solution could consist of creating two new packages for
> | cholmod-metis and klu-metis. Those new packages could change the
> | library names they produce adding a suffix (like "-metis") in order to
> | keep conflicts away while installing all together (libsuitesparse,
> | cholmod-metis and klu-metis).
> | Source packages for all them will be different.
> but then we need to split libsuitesparse in klu cholmod, umfpack, csparse ...
> for example if I install cholmod-metis but I still want to have umfpack and if
> cholmod-metis conflicts with libsuitesparse, then  no more umfpack.

Compiling suitesparse with metis give us only two different cholmod
and klu libraries, the rest remain the same. if libcholmod-metis would
install something like 'libcholmod-metis.so', it could live together
without conflicts with the libraries installed with libsuitesparse...
But yes, this is an ugly solution, only to keep different source
packages.

> Don't you think that a suitesparse-nonfree/metis package would be a simple
> solution ?

I think that means to maintain duplicated sources, what would be
interesting to prevent, but I fully agree, it seems to be the easier,
faster and cleaner solution.

Daniel