[MacPorts] #28799: New port: Play framwork
MacPorts
noreply at macports.org
Wed Apr 6 13:00:07 PDT 2011
#28799: New port: Play framwork
--------------------------------------+-------------------------------------
Reporter: ciserlohn@… | Owner: macports-tickets@…
Type: submission | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port: play
--------------------------------------+-------------------------------------
Comment(by ciserlohn@…):
''Replying to [comment:4 raimue@…]:
> The `worksrcdir` option is being changed in the pre-build phase. This
makes it impossible to run `build` and `destroot` as separate steps.
Either set this only once on the top-level or use
`build.dir`/`destroot.dir` instead to switch the working directory for the
command.
This was a workaround when I initially fetched the source with git (first
patch). These got fetched to the wrong directory because $worksrcpath is
defined in terms of $worksrcdir (see portmain.tcl) and portfetch::gitfetch
clones the sources to $worksrcpath. This means changing $worksrcdir causes
git.fetch (and hg.fetch too) to use the wrong directory. I open a separate
ticket for this after further investigation.
I wasn't aware of the 'build.dir' variable, there is no reference in the
documentation (except for the somewaht unrelated xcode portgroup). The
updated patch uses the 'build.dir' instead of changing the 'worksrcdir'.
> Why is the executable being installed into share and not directly into
bin?
> Does it have to be in the same directory as any resources?
Indeed. It expects to be located in the same directory as "framework",
"documentation", "resources", "modules" and "repositories"
--
Ticket URL: <https://trac.macports.org/ticket/28799#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list