On Tue, Nov 29, 2011 at 11:34:05AM +0000, Wookey wrote:
> But what is the correct thing to do in the control file for this
> transition? set Build-Depends: to
> libpng15-dev | libpng12-dev
> libpng12-dev | libpng15-dev
> libpng-dev
> libpng-dev | libpng12-dev
>
> I assume the last one is best: libpng-dev is presumably generic and
> will avoid this issue in the future, but is only in experimental
> currently so we should fallback to the existing libpng12-dev in the
> meantime. right?
The buildds will only ever take the *first* alternative to any build
dependency (and fail if that's not available), so practically speaking
you want to stick with libpng12-dev until the newer libpng hits
unstable.
After that, I guess the libpng maintainers have a plan that people
move to libpng-dev (presumably akin to libjpeg-dev).
> Eventually Build-depends could be changed to just 'libpng-dev' (The '|
> libpng12-dev' will remain useful for backports for a while after the
> wheezy release).
For autobuilt backports, the person doing the backport will need to edit
the control file to say libpng12-dev as the first (or only) alternative
anyway.
Cheers,
Olly
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
