On 2016/11/30 21:38, Jeremie Courreges-Anglas wrote: > Christian Weisgerber <[email protected]> writes: > > > On 2016-11-24, Christian Weisgerber <[email protected]> wrote: > > > >> Here's an update to graphics/tiff 4.0.7. > >> > >> Changes: > >> http://www.simplesystems.org/libtiff/v4.0.7.html > >> TL;DR: Numerous security fixes in the library; some tools were removed. > >> > >> Unfortunately some symbols were removed, necessitating a major bump. > >> This is problematic for -stable. > > > > The removed symbols are due to _static_ declarations in 4.0.7. We > > could revert that in -stable to maintain ABI compatibility. Does > > that sound sensible? > > It would be safer and more correct so +1 if it doesn't mean too many > patches.
I agree. > If keeping a strict ABI compatibility is too hard and the removed > symbols are obviously just internal details, I think we should we should > be allowed to cheat a bit for -stable. Of course there's always a risk > that some other port uses those internal details. If that were the case, for anything which is linked directly to an executable, linking would fail, so we should know about it from -current. That wouldn't be noticed during build for something which is a dlopen()'d module, but it does seem rather unlikely.
