BUG: ghostscript framework links against system zlib

[ehainry@…]

Previously, ghostscript depended on lib:libz:gzip, which is the correct way of putting it: there is no use installing gzip for building ghostscript on macosx.

[ryandesign (Ryan Carsten Schmidt)]

Well, wait a minute. MacPorts policy is to use its own software where possible unless there's a really good reason not to. However, according to the original specification, "libz" is the software being sought, but the gzip port does not provide that library. Rather, the zlib port does. So the ghostscript port should depend on the zlib port, not the gzip port.

Furthermore there is the problem that, while the ${prefix}/bin/gs binary is correctly linking against ${prefix}/lib/libz.1.dylib, ${prefix}/Library/Frameworks/Ghostscript.framework/Ghostscript is still linking against /usr/lib/libz.1.dylib which it shouldn't. (This is when I installed ghostscript +gslib.)

[ehainry@…]

Oops, you are right, I was wrong saying that lib:libz:gzip was the correct way dependency. However, it is true that ghostscript does not need macports' gzip to build (and in fact does not seem to link against anything in port:gzip).

So port:gzip should be replaced by port:zlib.

[ryandesign (Ryan Carsten Schmidt)]

Since no response from maintainer, I changed the dependency from gzip to zlib in r29804.

The framework issue I reported above still remains.

[takanori@…]

Fixed in r36106.

[(none)]

Milestone Port Bugs deleted