2021.01.10 16:18 "Re: [Tiff] Motions related to C99 use in libtiff", by Greg Troxel

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

I am with Bob. I tried to say that changing was ok as long as there was a compat plan that gave some reasonable period fo time for depending packages to adapt, where reasonable is perhaps 2 years. That part was dropped from my comments, and that makes me wonder who else gave compat caveats.

I do think that "tiff won't build unless the compiler is C99" is fine.

For an API break, I did say that for pkgsrc I could deal with adding flags to depending packages. That doesn't mean I think that's what we should do, just that I could live with it, in a rare moment of me not being super difficult :-)

I also hadn't really thought of an opt-in define. Indeed, that's easy to add when updating a depending program, and it makes everything pretty simple.

I get Even's point that some packages won't update. It's fair to push work onto them when they haven't after some reasonable period of time, but this is just being talked about and there is not yet a new way, so it's not fair to impose a rush on them.

And, programs are going to have to deal with the new way and the old way for a long time. Some systems are going to have older tiff for a while. At some point, like a LTS that froze things in 2014, that gets crazy. But again we are talking about the reasonable window being a few years.

So I see this vote as a 'in principle we should move in this direction' and do not believe it represents any kind of consensus about breaking depending apps.