Hacking in Universal -- Don't!
Jordan K. Hubbard
jkh at brierdr.com
Sat Mar 31 14:38:13 PDT 2007
Which private API are you referring to?
I know that the port was *broken* until I changed it to use the right
command API, but that had nothing to do with building universal, that
was a very hacky way of building the static archive.
On Mar 31, 2007, at 10:28 AM, Landon Fuller wrote:
> I received a bug report about the zlib port not working -- it was
> modified to use private API in an attempt to hack in Universal
> The port, which I originally wrote in 2003, went from this:
> to this:
> This is not an improvement! The port is literally twice as long,
> but more importantly, it *FAILS* on different versions of MacPorts
> because it uses MacPorts-private undocumented API calls.
> I believe we need a very straight-forward policy:
> - Do not use undocumented, private API in Portfiles. This will
> cause breakage and make the system entirely unmaintainable.
> - If making a Portfile "Universal" complicates the Portfile, then
> you need to patch the software, not the port.
> macports-dev mailing list
> macports-dev at lists.macosforge.org
More information about the macports-dev