2021.01.04 14:23 "[Tiff] Motions related to C99 use in libtiff", by Even Rouault

2021.01.10 14:54 "Re: [Tiff] Motions related to C99 use in libtiff", by Bob Friesenhahn

trying to sum up votes,

Motion 1:
+1: Even Rouault, Olivier Paquet, Greg Troxel, Kurt Schwehr, Kemp Watson, Jeff Breidenbach, Roger Leigh (I assume!)
No vote: Edward Lam, William Bader, Bob Friesenhahn

Motion 2:
+1: Even Rouault, Olivier Paquet, Greg Troxel, Kurt Schwehr, Kemp Watson, Roger Leigh (I assume!)
-1: Jeff Breidenbach
No vote: Edward Lam, William Bader, Bob Friesenhahn

So both are passed

While I can support Motion 1 and even some definition of Motion 2, my repeatedly-expressed concerns were never addressed.

I can not support a solution which will result in most existing applications to fail to compile by default. I do support a solution which allows an appropriately updated application (or build framework) to inform libtiff headers that dependent source code is prepared for the new typedefs (and thus depending on them), while allowing unprepared applications to still compile by default. Note that this is different than an application informing libtiff that it still needs to old definitions because that would require that the application (or the framework building it) be updated already.

For some number of years, applications which have been updated for the new typedefs will be exposed to older libtiffs which have not been updated. There needs to be a way for applications which have been updated to detect use of an older libtiff which does not support/provide the new typedefs. Unless there is a seamless transition, there will be chaos. The transition mechanism could be removed after a couple of years, (which seems to be a typical major update interval) or left in place a bit longer in case there are observed update issues.

You are the one who came up with the definitions for these motions, without any necessary agreement that this limited set of motions is the set that should be considered.

Once again, breaking the build by default for the major proportion of apps depending on libtiff is not an option that I can support.

Bob

Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt