[Pkg-crosswire-devel] qtwebkit packaging changes in Maverick?

[Daniel Glassey]

On Wed, Nov 10, 2010 at 5:48 AM, Jonathan Marsden <jmarsden at fastmail.fm> wrote:
> I'm packaging BibleTime 2.8_rc1 for Debian and Ubuntu.
>
> My packages currently build and seem to basically work on Debian stable
> and unstable, and on Ubuntu Lucid.
>
> They fail to build on Debian experimental or on Ubuntu Maverick or
> Natty!  This is apparently because the packaging of qtwebkit changed or
> is being changed.  In particular, the header file QWebSettings used to
> be part of libqt4-dev, but in Maverick and Natty it is not there, it is
> in libqtwebit-dev instead.  But libqtwebkit-dev does not exist in Lucid.
>
> This is awkward, since I'd like a BT package that builds for both Lucid
> and for Maverick and Natty...  I'm thinking about kludges such as
>
> Build-Depends: libqtwebkit-dev | libqt4-dev
>
> so that if libqtwebkit-dev exists for a given setup it will be installed
> and used, but if not it will fall back to libqt4-dev which is needed
> anyway and will always be found and installed/used.
>
> But that's pretty ugly.  Is there some better way of doing "If building
> for distro X then Build-Depends on package Y"?  Or do I just need to
> keep two /debian source trees in parallel from now on, one for Lucid and
> one for Maverick and Natty??

I haven't thought of other options so far but those dependencies
should be versioned i.e.  libqtwebkit-dev | libqt4-dev (<= version
QWebSettings was last in it)

Alternatively this blog post explains a way to do different
dependencies in different distros - though I haven't tried it to see
if it works for different releases of the same distro as well.

http://raphaelhertzog.com/2010/09/27/different-dependencies-between-debian-and-ubuntu-but-common-source-package/

HTH,
Daniel