On May 25, 2015, at 4:38 AM, René J.V. Bertin wrote: > Exactly; even if you can actually show a significant benefit to libjpeg-turbo > in your application that doesn't mean that benefit exists in enough ports > across the board to warrant forcing all ports to be rebuilt against it.
What warrants rebuilding all ports against libjpeg-turbo is the simplicity of having a single official jpeg library in MacPorts. I don't want to complicate things by having some ports link with libjpeg-turbo and others link with libjpeg. > In that case there would just be the need for something like a port_select > mechanism to let libjpeg.dylib point to the library of choice, and make the > appropriate headers available. In turn, installed ports will continue to > function after switching the selected jpeg library, even if port:jpeg > continues to provide v9. Definitely not going to use port select for the jpeg libraries. It is inappropriate for the effects of port select to be used by other ports. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
