dolfin team mailing list archive

[Julien Cristau <jcristau@xxxxxxxxxx>]

On Fri, Jun 15, 2012 at 10:32:56 +0200, Johannes Ring wrote:

> On Thu, Jun 14, 2012 at 4:46 PM, Julien Cristau
> <julien.cristau@xxxxxxxxxx> wrote:
> > If dolfin only works with the version of swig it was built against, that
> > needs to be reflected in the package dependencies.
> 
> Okay, but I'm unsure how to do that. Currently I have "Build-Depends:
> swig2.0" in the source package and "Depends: swig2.0" in the binary
> package python-dolfin. What should I put there instead? Are you
> suggesting that I should add something like "{Build-}Depends: swig2.0
> (>= 2.0.7), swig2.0 (<< 2.0.8)"? Wouldn't that require me to do a new
> upload when swig 2.0.8 is added in the future? If so, is that any
> better than doing binNMU's?
> 
I'm suggesting you should leave your build-depends alone, check at
build-time what the swig version is, and generate a Depends on that
(upstream) version.  binNMUs would still work, and you wouldn't get an
installable but broken package.

Cheers,
Julien