Hi Artur,
Artur Rona wrote:
> If you'd change those Build-Depends, then when the libtiff5
> transition starts in Debian, this package will only need a binNMU
> (which can be done in bulk by the release team) rather than a
> coordinated upload.
Ok, granted. Thanks for the explanation.
> There's only a single provider of libtiff-dev at any one time, so
> it's fine to build-depend directly on it without additionally
> stating a real alternative (saving a time).
And this seems to be the case even in Squeeze, hence even a backport
to oldstable-backports-sloppy wouldn't be hindered by removing the
alternative build-dependencies. (IIRC that was my fear the last time I
looked at it.)
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
