Dear Folk,
The reference was enlightening, but what does ${worksrcpath} mean? It is part
of the definitions for configure, build, and destroot. Ultimately it's defined
in terms of ${portbuildpath} which has only one use on that page in the
definition of workpath. ???
More is better than less when it comes to definitions.
Shalom,
John B. Brown.
[[email protected]]
358 High Street,
Buffalo, Wyoming
82834
"Freedom is not worth having if it does not include
the freedom to make mistakes" Mahatma Gandhi
"There was never a good war or a bad peace."
Benjamin Franklin
"I wonder whether the world is being run
by smart people who are putting us on
or by imbeciles who really mean it." Mark Twain
1-307-684-9068
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.
------------------------------------------------------------------------
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
