2021.01.05 17:12 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault

I see your point. Just realize thought that this is asking packagers to choose between

• not updating tiff
• patching everything that depends on tiff
• dropping tiff as a dependency for things where that is sane (maybe emacs)
• dropping things that depend on tiff and things that depend on them

I'm going to choose not updating tiff until the pain is pushed around and the other packages that depend on it (the ones that matter) have been updated.

As pointed out by Roger,

https://gitlab.com/rleigh/libtiff/-/blob/ bb0c8ac183e263759ed9e6a6c0563d35b9459c77/libtiff/tiff.h#L68

there's actually an easy way to make packages that wouldn't change their source code to still compile by setting -DTIFF_LEGACY_TYPES That should hopefully make packagers' effort reasonable.

Even

Spatialys - Geospatial professional services
http://www.spatialys.com