local portindex failing on net/tcpflow - macosx_deployment_target
Hi In my local ports repository, portindex is failing when running on net/tcpflow with the following error: Error: Error executing darwin_9: invalid command name "macosx_deployment_target" Failed to parse file net/tcpflow/Portfile: Error evaluating variants Any idea why this is happening in my local ports repository, yet not in the master repository? I'm running the latest 1.520 release. Cheers Adam
On Nov 5, 2007, at 9:45 AM, Adam Mercer wrote:
Any idea why this is happening in my local ports repository, yet not in the master repository? I'm running the latest 1.520 release.
The portindex in the repository is generated on my machine which currently runs 10.4. You appear to be running on 10.5, so the darwin 9 platform variant gets run on your machine, but not on on mine. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On 05/11/2007, Daniel J. Luke <dluke@geeklair.net> wrote:
The portindex in the repository is generated on my machine which currently runs 10.4.
You appear to be running on 10.5, so the darwin 9 platform variant gets run on your machine, but not on on mine.
Thanks, I was worrying that there was something strange with my installation. Cheers Adam
On Nov 5, 2007, at 10:38, Adam Mercer wrote:
On 05/11/2007, Daniel J. Luke wrote:
On Nov 5, 2007, at 08:45, Adam Mercer wrote:
In my local ports repository, portindex is failing when running on net/tcpflow with the following error:
Error: Error executing darwin_9: invalid command name "macosx_deployment_target" Failed to parse file net/tcpflow/Portfile: Error evaluating variants
Any idea why this is happening in my local ports repository, yet not in the master repository? I'm running the latest 1.520 release.
The portindex in the repository is generated on my machine which currently runs 10.4.
You appear to be running on 10.5, so the darwin 9 platform variant gets run on your machine, but not on on mine.
Thanks, I was worrying that there was something strange with my installation.
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.
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 +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
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 +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
On Nov 5, 2007, at 14:01, Kevin Ballard wrote:
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)
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.
That, and the restart-netchange option. But not all of trunk, yet (specifically not the removal of the cd command).
participants (4)
-
Adam Mercer
-
Daniel J. Luke
-
Kevin Ballard
-
Ryan Schmidt