Luk Claes l...@debian.org wrote:
Your plan looks good except that I think it would be better to have
libtiff5-dev provide libtiff-dev and not introduce a proper libtiff-dev.
Thanks for the reply. That's fine, I can make that modification.
Rereading my plan all the way through, I think having
Hi Jay
Your plan looks good except that I think it would be better to have
libtiff5-dev provide libtiff-dev and not introduce a proper libtiff-dev.
Cheers
Luk
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi Jay
Disclaimer, I'm not part of the release team but have only one comment
on the message below:
On Sat, Jun 01, 2013 at 02:55:40PM -0400, Jay Berkenbilt wrote:
It's been a few weeks since my original post about the libtiff
transition, and I haven't heard any responses. While I appreciate
It's been a few weeks since my original post about the libtiff
transition, and I haven't heard any responses. While I appreciate that
this is not at the top of your long list, I would really appreciate some
kind of response if only an indication that you've got it on your list
and will prioritize
I'm not sure where the tiff transition falls on your long list, but I
thought I'd add a little more information on what issues we may
encounter.
Jay Berkenbilt q...@debian.org wrote:
Wasting no time, I'd like to remind the release team that I'm really
hoping Jessie will ship with only one
Jay Berkenbilt qjb at debian.org writes:
hoping Jessie will ship with only one version of the tiff library:
[…]
I'd obviously like to get on this as soon as possible, but I understand
Agreed, but tiff depends on jpeg, and there are people who want to switch
jpeg to “jpeg-turbo” (still being
6 matches
Mail list logo
