It's been a little over a month since my announcement to debian-devel
that I would be preparing to remove the tiff3 package from debian and
asking people to switch build dependencies on libtiff4-dev to
libtiff-dev. There are 64 packages that have a version in either
testing, unstable, or experimen
On 06/12/13 20:48, Philipp Kern wrote:
> So if you version your -dev package, do not install into an unversioned
> place like libtiff5-dev does. :)
It seems to me that the good options are:
* one unversioned -dev package, on the default gcc include path and/or
relying on pkg-config to get the a
On Fri, Dec 06, 2013 at 02:38:47PM +, Sune Vuorela wrote:
> On 2013-12-06, Thorsten Glaser wrote:
> > Hm indeed. Makes me wonder whether it would not be better to make
> > libtiff-dev the real package and abandon libtiffN-dev altogether.
> > (Never understood why the -dev packages need the num
Sune Vuorela wrote:
> On 2013-12-06, Thorsten Glaser wrote:
>> Hm indeed. Makes me wonder whether it would not be better to make
>> libtiff-dev the real package and abandon libtiffN-dev altogether.
>> (Never understood why the -dev packages need the numbers, anyway.)
>
> The -dev packages needs
On 2013-12-06, Thorsten Glaser wrote:
> Hm indeed. Makes me wonder whether it would not be better to make
> libtiff-dev the real package and abandon libtiffN-dev altogether.
> (Never understood why the -dev packages need the numbers, anyway.)
The -dev packages needs numbers if you want to have se
Simon McVittie wrote:
>As far as I can see, changing from (libtiffN-dev Provides libtiff-dev,
>libtiff(N+1)-dev does not) to the other way round has an inherent race
Hm indeed. Makes me wonder whether it would not be better to make
libtiff-dev the real package and abandon libtiffN-dev altogether.
On 06/12/13 10:56, Colin Watson wrote:
> On Fri, Dec 06, 2013 at 10:19:14AM +0100, Thorsten Glaser wrote:
>> On Thu, 5 Dec 2013, Jay Berkenbilt wrote:
>>> * If your package build-depends on libtiff5-dev, you don't HAVE to do
>>>anything, but you may be helping yourself in the future if you cha
On Fri, Dec 06, 2013 at 10:19:14AM +0100, Thorsten Glaser wrote:
> On Thu, 5 Dec 2013, Jay Berkenbilt wrote:
> > * If your package build-depends on libtiff5-dev, you don't HAVE to do
> >anything, but you may be helping yourself in the future if you change
> >the build dependency to libtiff
On Thu, 5 Dec 2013, Jay Berkenbilt wrote:
> * If your package build-depends on libtiff5-dev, you don't HAVE to do
>anything, but you may be helping yourself in the future if you change
>the build dependency to libtiff-dev (>> 4.0.3-6~).
Uhm, I have a rather general question here.
libtiff
Once sentence summary: if your package has a build dependency on
libtiff4-dev, libtiff5-dev, or libtiff5-alt-dev, you will probably just
want to change the build dependency to be on libtiff-dev, but there are
some special cases, so read on if in doubt.
[As I write this, the tiff 4.0.3-6 is not bu
10 matches
Mail list logo
