Hi,
> I meant, you upload your package built against libtiff4-dev, which is
> the status quo. However, you do a build-test where you swap
> libtiff4-dev with libtiff5-dev to see if your package would compile if
> libtiff5-dev had been used instead of libtiff4-dev. So when the time
> comes, all you have to do, is to swap libtiff4-dev with libtiff5-dev.
I conclude from that, that I should *in general* not use libtiff5-dev
right now? Having a apckage build *only* against libtiff5-dev is not
acceptable, although the package is there and already has dependencies?
I'd like to get a clear answer from the release team, if I:
a) should upload the package without touching anything libtiff-related,
b) should upload the package with a versioned libtiff5 dependency,
c) should patch the code to build against both and use an unversioned
Build-Depends.
Cheers,
Nik
--
* concerning Mozilla code leaking assertion failures to tty without D-BUS *
<mirabilos> That means, D-BUS is a tool that makes software look better
than it actually is.
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Attachment:
signature.asc
Description: Digital signature