On Dec 8, 2011, at 8:52 AM, John B Brown wrote:
> Jeremy Lavergne wrote:
>>> Any help? (really my reason for writing this is "shouldn't there be a
>>> $ port make or shouldn't $ port build re-run it?
>>
>> You might become familiar with the various phases available:
>> http://guide.macports.org/#reference.phases
>> or the man page.
>> Rather than going past all the phases and installing the package, you might
>> consider completing only the phases before where you need the modify the
>> package source code and then running the remainder.
>> As you did in your previous email, keep -s on so you don't accidentally
>> clobber all your work with a pre-built binary from MacPorts.
>
> The reference was enlightening, but what does ${worksrcpath} mean?
>From the same page:
worksrcpath
Full path to extracted source code.
Value: ${workpath}/${worksrcdir}
Because ${worksrcpath} can be changed by adding a "worksrcdir" the description
might better read:
Full path to directory where port commands are executed from.
Look at the definition for "worksrcdir" on the same page.
Regards,
Bradley Giesbrecht (pixilla)
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
