[MacPorts] Notification: howto/RunningTrunk modified

[MacPorts]

Changed page "howto/RunningTrunk" by ryandesign at macports.org from 75.54.82.179*
Page URL: <http://trac.macports.org/wiki/howto/RunningTrunk>
Diff URL: <http://trac.macports.org/wiki/howto/RunningTrunk?action=diff&version=7>
Revision 7

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: howto/RunningTrunk
=========================================================================
--- howto/RunningTrunk (version: 6)
+++ howto/RunningTrunk (version: 7)
@@ -11,21 +11,22 @@
 
 == Installation ==
 
-=== Step 1: '''Checkout MacPorts trunk''' ===
+=== Step 1: '''Check out MacPorts trunk''' ===
 
-Pick a location to store MacPorts; for this HOWTO {{{/opt/mports}}} will be used (change to suit); run
+Pick a location to store a working copy of the MacPorts code. For this HOWTO {{{/opt/mports}}} will be used (change to suit). Run:
 {{{
+mkdir -p /opt/mports
 cd /opt/mports
 svn co http://svn.macports.org/repository/macports/trunk
 }}}
-which will create {{{/opt/mports/trunk}}} containing everything needed for MacPorts.
+This will create {{{/opt/mports/trunk}}} containing everything needed for MacPorts.
 
 === Step 2: '''Build and Install MacPorts''' ===
 
-Build and install MacPorts with:
+Build and install MacPorts:
 {{{
 cd /opt/mports/trunk/base
-./configure
+./configure --enable-readline
 make
 sudo make install
 make distclean
@@ -36,16 +37,16 @@
 
 === Step 3: '''Configure MacPorts to use port information from subversion''' ===
 
-Open {{{/opt/local/etc/macports/sources.conf}}} in a text editor.  Change the last line which should look like
+Open {{{/opt/local/etc/macports/sources.conf}}} in a text editor.  The last line which should look like this:
 {{{
 rsync://rsync.macports.org/release/ports/
 }}}
-to point to the stuff you already checked out:
+Change it to point to the working copy you checked out:
 {{{
 file:///opt/mports/trunk/dports
 }}}
 
-Now MacPorts will look in the subversion checkout for port information.
+Now MacPorts will look for portfiles in the working copy.
 
 === Step 4: '''Update PATH''' ===
 
@@ -57,12 +58,11 @@
 
 === '''Subversion update''' ===
 
-The official release of MacPorts has two commands {{{sync}}} and {{{selfupdate}}}, used to update all the port information ({{{sync}}}) and to update the base MacPorts installation when necessary ({{{selfupdate}}}).  Instead of using these, update the subversion files:
+MacPorts has two commands used to keep itself current: {{{sync}}}, used to update the ports tree, and {{{selfupdate}}}, to update the MacPorts base code. When compiling MacPorts yourself instead of using a released MacPorts package, you can continue to use {{{sync}}} to update the ports tree, or you can update the working copy manually like this:
 {{{
-cd /opt/mports/trunk
-svn update
+svn update /opt/mports/trunk
 }}}
-does what {{{port sync}}} would do.  You do need to update the base install manually however, when and/or if needed, with the same commands listed in step 2 above.
+You should not use {{{selfupdate}}} anymore because it would downgrade you to the latest released version of MacPorts. Instead you should {{{svn update}}} as above and then repeat the steps listed in step 2 above.
 
 == Using MacPorts ==
 At this point, most things should work like they do for anyone else; you will encounter some newer functionality that hasn't found its way to a release yet, and occasionally a bug.  If so, be sure to [http://trac.macports.org/newticket report the bug] when it happens.
@@ -76,6 +76,6 @@
 Warning: the following items did not execute (for [PORTNAME]): org.macports.activate org.macports.destroot org.macports.install
 Error: Status 1 encountered during processing.
 }}} 
-It was never really intended to be used in portfiles, and it got removed because of it was considered confusing for it's side-effects. See #12914 for a few more details and Ryan Schmidt's explanation on the dev list [http://lists.macosforge.org/pipermail/macports-dev/2008-July/005652.html in this mail]. If you encounter this problem with a port, please file a bug against this port which still uses {{{cd}}}. 
+It was never really intended to be used in portfiles, and it got removed because the side-effects of using it can be confusing. See #12914 for more details and Ryan Schmidt's explanation on the dev list [http://lists.macosforge.org/pipermail/macports-dev/2008-July/005652.html in this mail]. If you encounter this problem with a port, please file a bug against this port which still uses {{{cd}}}. 
 
 [wiki:howto <- Back to the HOWTO section]

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


* The IP shown here might not mean anything if the user 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 MacPorts.
If it was not you, please report to http://www.macports.org/.