[MacPorts] CommittersTipsAndTricks modified

MacPorts noreply at macports.org
Mon Oct 25 10:54:14 PDT 2010


Changed page "CommittersTipsAndTricks" by jjstickel at vcn.com from 192.174.37.51*
Page URL: <https://trac.macports.org/wiki/CommittersTipsAndTricks>
Diff URL: <https://trac.macports.org/wiki/CommittersTipsAndTricks?action=diff&version=36>
Revision 36

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: CommittersTipsAndTricks
=========================================================================
--- CommittersTipsAndTricks (version: 35)
+++ CommittersTipsAndTricks (version: 36)
@@ -299,3 +299,20 @@
 sha1 a37874511946ba340d5df2d92252177f9eb906f6 \
 rmd160 1f842ea95ad6dd2cba2cdc2d2bd8e0be5063fb9b
 }}}
+
+== Testing Port Phases ==
+
+Individual port phases (extract, patch, configure, build, etc.) can be run by using the appropriate keyword:
+{{{
+port build python26
+}}}
+All phases that have not already been performed up to the designated phase will be run.  If you want to rerun a port command that completed successfully, you can edit ./work/.macports.[port name].state and remove the lines up to the completed stage you want to keep.
+
+By default, if the portfile is changed, you will get the message:
+{{{
+Portfile changed since last build; discarding previous state.
+}}}
+and the build directory will be removed (cleaned) before proceeding.  When debugging a portfile, this can be avoided by using the '-o' flag (from the manpage):
+{{{
+-o       honor state files older than Portfile
+}}}

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on CommittersTipsAndTricks. If it was not you, please
report to .


More information about the macports-changes mailing list