Hacking in Universal -- Don't!

[Jordan K. Hubbard]

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.

- Jordan

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  
> support.
>
> The port, which I originally wrote in 2003, went from this:
> 	http://trac.macports.org/projects/macports/browser/trunk/dports/ 
> archivers/zlib/Portfile?rev=23414
> to this:
> 	http://trac.macports.org/projects/macports/browser/trunk/dports/ 
> archivers/zlib/Portfile?rev=22776
>
> 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.
>
> -landonf
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-dev