Re: [23788] trunk/dports/aqua/macsword/Portfile
On Apr 9, 2007, at 8:49 PM, source_changes@macosforge.org wrote:
Log Message Fix app bundle path for newer Xcodes.
Modified Paths • trunk/dports/aqua/macsword/Portfile
---snip---
destroot { xinstall -d -m 0755 ${destroot}/Applications/MacPorts - system "cp -R ${worksrcpath}/build/MacSword.app \ + system "cp -R ${worksrcpath}/build/Deployment/MacSword.app \ ${destroot}/Applications/MacPorts" }
Shouldn't these paths and Xcode settings be handled through the Xcode PortGroup? -jmpp
On Apr 9, 2007, at 20:21, Juan Manuel Palacios wrote:
destroot { xinstall -d -m 0755 ${destroot}/Applications/MacPorts - system "cp -R ${worksrcpath}/build/MacSword.app \ + system "cp -R ${worksrcpath}/build/Deployment/MacSword.app \ ${destroot}/Applications/MacPorts" }
Shouldn't these paths and Xcode settings be handled through the Xcode PortGroup?
What does the Xcode PortGroup do? What does any PortGroup do? I'm not familiar with the concept of a PortGroup, and searching the documentation index [1] for "group" does not seem to show anything relevant. [1] http://web.archive.org/web/20060427120406/http:// darwinports.opendarwin.org/docs/
the portgroups are installed to ${prefix}/share/darwinports/resources/ port1.0/group/. they're also available online[1]. [1] http://svn.macports.org/repository/macports/trunk/base/src/ port1.0/resources/group/ Regards, Elias On Apr 10, 2007, at 4:16 AM, Ryan Schmidt wrote:
What does the Xcode PortGroup do? What does any PortGroup do? I'm not familiar with the concept of a PortGroup, and searching the documentation index [1] for "group" does not seem to show anything relevant.
[1] http://web.archive.org/web/20060427120406/http:// darwinports.opendarwin.org/docs/
On Apr 9, 2007, at 10:24 PM, Elias Pipping wrote:
the portgroups are installed to ${prefix}/share/darwinports/resources/port1.0/group/.
they're also available online[1].
[1] http://svn.macports.org/repository/macports/trunk/base/src/port1.0/ resources/group/
Regards,
Elias
There's also the portgroup(7) man page, which can of course tell you all a Portfile writer should know about the particular group he/she is using (or, at least, as much as was written for it ;-) HTH! -jmpp PS: Obviously reeding the PortGroup sources is also an approach, but arguably everything should be in the man page.
participants (3)
-
Elias Pipping
-
Juan Manuel Palacios
-
Ryan Schmidt