Re: Plans for ITK version 4
- To: Yaroslav Halchenko <debian@onerussian.com>
- Cc: Paul Novotny <paul@paulnovo.us>, "Steve M. Robbins" <steve@sumost.ca>, debian-med@lists.debian.org
- Subject: Re: Plans for ITK version 4
- From: Jay Berkenbilt <qjb@debian.org>
- Date: Sat, 19 May 2012 10:48:19 -0400
- Message-id: <[🔎] 20120519104819.1611911245.qww314159@soup>
- In-reply-to: <20120320090641.2124876422.qww314159@jberkenbilt-linux.appiancorp.com> (Jay Berkenbilt's message of "Tue, 20 Mar 2012 09:06:47 -0400")
- References: <20120124035316.GL4627@sumost.ca> <CAAvaLCyGoxUpopbS4hEg5GqbRqfLqV5fG9TG38=hzPWw7pAfnw@mail.gmail.com> <20120128094342.GB15943@sumost.ca> <CAAvaLCzZVT5cknrcJj9hFqZGcA4pdNb9xaxqgJGbn113v=3k4w@mail.gmail.com> <20120128184751.GA8009@sumost.ca> <20120302144750.GA14834@onerussian.com> <20120303003909.GD14039@sumost.ca> <CABAUzPqf=-JaAj9+S4tWGDiD4CVwR4KKjiPiS6V504G3N2Qn-w@mail.gmail.com> <20120304190930.GP14039@sumost.ca> <1332190002.4407.9.camel@PaulDesktop> <20120319232515.GF22869@onerussian.com> <20120320090641.2124876422.qww314159@jberkenbilt-linux.appiancorp.com>
I'm quoting the entire old thread below since it's been a while, but I
have a solution now unless the release team rejects it.
> Yaroslav Halchenko <debian@onerussian.com> wrote:
>
> there seems to be a new build-depends complication:
>
> libgeotiff-dev depends on libtiff5-dev,
>
> libtiff5-dev is not (yet) providing libtiff-dev (but conflicting
> with libtiff4-dev providing
> it)
>
> itk4 and libvtk5-dev depending on libtiff-dev
>
> that makes it impossible to satisfy build-depends (tried on sparc)...
>
> but now I am totally confused:
>
> http://packages.debian.org/search?keywords=libtiff5-dev
> says that
>
> experimental: Virtual package
> provided by: libtiff-dev
>
> but http://packages.debian.org/experimental/libtiff-dev
> Package: libtiff-dev (4.0.0~beta6-3 and others)
> mentions it available only for alpha and hppa
>
> Jay -- could you please clarify the situation? what is that libtiff-dev source
> package in experimental ? or/and when libtiff5-dev would provide
> libtiff-dev?
>
> or am I missing the point here?
You had pointed out before that libtiff5-dev and libtiff4-dev can't be
installed at the same time, which makes it impossible for something with
an indirect dependency on libtiff4-dev to have a dependency on
libtiff5-dev. The release team has rejected a few of my approaches to
fixing this (until after wheezy, at which point, plan A can be
implemented). In the interim, I'm planning on uploading
libtiff5-alt-dev, which installs the libtiff5-dev files in a location
that doesn't conflict with libtiff4-dev. You can then make your package
build depend on libtiff5-alt-dev instead. If your package uses
pkg-config to find the tiff headers and libraries, you don't have do
anything else -- this will just work. If it doesn't use this, then you
can set your include and library paths manually based on the output of
pkg-config --cflags libtiff-4 and pkg-config --libs libtiff-4.
If all goes well, I will do the upload today, and the packages will
appear whenever they clear NEW. Does this sound okay?
--
Jay Berkenbilt <qjb@debian.org>
Reply to: