Actually, it's exactly the opposite: currently libwt-dev depends on
the most recent version of Boost:
Package: libwt-dev
Depends: ${shlibs:Depends}, ${cli:Depends}, ${misc:Depends},
libwt32 (= ${binary:Version}),
libboost-dev (>= 1.36.0), libboost-date-time-dev (>= 1.36.0),
libssl-dev, libfcgi-dev, libboost-filesystem-dev (>= 1.36.0),
libboost-regex-dev (>=1.36.0),
libboost-signals-dev (>= 1.36.0), libboost-thread-dev (>= 1.36.0)
I'm not 100% sure yet but this is my guess:
1. Wt is build agains the latest version of Boost at the moment, say
1.46.1. Via shlibs, this means libwt32, libwthttp32, etc (the binary
packages) depend on a particular version of the binary packages of
Boost: libboos-program-options1.46.1, libboost-random1.46.1, etc. Yet
libwt-dev still depends on the latest version of Boost, provided via
libboost-dev.
2. The default version of Boost (package libboost-dev) is updated
3. When you install libwt-dev, there is a silent problem you will not
notice until you try to compile: libboost-dev is now different from
libboost-dev when Wt was built.
The ideal solution would be to have something like ${shlib:Depends}
but for libboost-dev packages. AFAIK there is no such thing, though
:-/
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
