[Pkg-scicomp-devel] paraview: builds against python2.5-dev if that is installed
jorrit at jorrit.de
Wed Feb 27 14:57:31 UTC 2008
Am Wed, 27. Feb 2008, 14:14:50 +0100 schrieb Ondrej Certik:
> Do you suggest to change the build depend to python2.4-dev? This
> wouldn't imho change anything -
> if python2.5-dev is installed, it will use it too.
I can't think of a clean solution, so I didn't mean to suggest anything.
AFAICT the intent was to trace the default python in Debian, thus the
build-dep on python-dev. Changing that to python2.4-dev does help as you
noted. Other options are:
* Build-Dep: python-dev and Build-Conflict: python2.5-dev
This will give a FTBFS when Debians default Python changes to 2.5.
* Build-Dep: python2.4-dev and Build-Conflict: python2.5-dev
This does not trace Debians default Python anymore.
* Patch paraviews config to look for a specific version of python
It looks like python-config will print out the build configuration of the
default python. However, I have no idea of cmake and how it checks for
installed packages so I don't know how feasible this is.
> I only test the
> build in pbuilder, and there it is never
> a problem. And buildds will not have python2.5 either.
Are buildds now always installed from scratch for each build? In that case
it's probably OK as it is now.
My (somewhat dated) last information was that they just install/remove enough
packages to satisfy the build-deps.
* >aylee #macht ist voellig aus dem Haeusschen und kuesst den Drucker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-scicomp-devel/attachments/20080227/2253094c/attachment.pgp
More information about the Pkg-scicomp-devel