On the contrary, I think we need to push out a release with
macosx_deployment_target. I foresee many more ports needing to use
that variable, so we should make it available now.
On Nov 5, 2007, at 1:43 PM, Daniel J. Luke wrote:
On Nov 5, 2007, at 12:40 PM, Ryan Schmidt wrote:
Well, but wait, this means that the tcpflow port cannot be used on
Mac OS X Leopard unless the user builds MacPorts from trunk, right?
macosx_deployment_target wasn't added to MacPorts until r30396 on
October 26, 2007. And I thought we always want to keep our ports
working on the currently-released version of MacPorts.
Right, the tcpflow port should probably be changed (at least until a
macports release contains macosx_deployment_target)
--
Daniel J. Luke
+========================================================+
| *---------------- [EMAIL PROTECTED] ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
--
Kevin Ballard
http://kevin.sb.org
[EMAIL PROTECTED]
http://www.tildesoft.com
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
