Orion Poplawski <or...@cora.nwra.com> writes:
> BR of libjpeg-devel now pulls in libjpeg-turbo-compat-devel, but this doesn't
> really work as a drop in replacement because those headers are in
> /usr/include/libjpeg-turbo-compat/.
Yeah, I just whinged about that at bz #887013.
> Shouldn't libjpeb-turbo-devel provide
> libjpeg-devel and not libjpeg-turbo-compat-devel?
Only if jpeg8 is a drop-in (source code compatible) replacement.
Otherwise you're only moving the point at which failures will occur.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
