Changes between Version 6 and Version 7 of howto/RunningMaster
- Timestamp:
- Jul 25, 2008, 12:50:08 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
howto/RunningMaster
v6 v7 12 12 == Installation == 13 13 14 === Step 1: '''Check out MacPorts trunk''' ===14 === Step 1: '''Check out MacPorts trunk''' === 15 15 16 Pick a location to store MacPorts; for this HOWTO {{{/opt/mports}}} will be used (change to suit); run16 Pick a location to store a working copy of the MacPorts code. For this HOWTO {{{/opt/mports}}} will be used (change to suit). Run: 17 17 {{{ 18 mkdir -p /opt/mports 18 19 cd /opt/mports 19 20 svn co http://svn.macports.org/repository/macports/trunk 20 21 }}} 21 whichwill create {{{/opt/mports/trunk}}} containing everything needed for MacPorts.22 This will create {{{/opt/mports/trunk}}} containing everything needed for MacPorts. 22 23 23 24 === Step 2: '''Build and Install MacPorts''' === 24 25 25 Build and install MacPorts with:26 Build and install MacPorts: 26 27 {{{ 27 28 cd /opt/mports/trunk/base 28 ./configure 29 ./configure --enable-readline 29 30 make 30 31 sudo make install … … 37 38 === Step 3: '''Configure MacPorts to use port information from subversion''' === 38 39 39 Open {{{/opt/local/etc/macports/sources.conf}}} in a text editor. Change the last line which should look like40 Open {{{/opt/local/etc/macports/sources.conf}}} in a text editor. The last line which should look like this: 40 41 {{{ 41 42 rsync://rsync.macports.org/release/ports/ 42 43 }}} 43 to point to the stuff you alreadychecked out:44 Change it to point to the working copy you checked out: 44 45 {{{ 45 46 file:///opt/mports/trunk/dports 46 47 }}} 47 48 48 Now MacPorts will look in the subversion checkout for port information.49 Now MacPorts will look for portfiles in the working copy. 49 50 50 51 === Step 4: '''Update PATH''' === … … 58 59 === '''Subversion update''' === 59 60 60 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:61 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: 61 62 {{{ 62 cd /opt/mports/trunk 63 svn update 63 svn update /opt/mports/trunk 64 64 }}} 65 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.65 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. 66 66 67 67 == Using MacPorts == … … 77 77 Error: Status 1 encountered during processing. 78 78 }}} 79 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 fewmore 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}}}.79 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}}}. 80 80 81 81 [wiki:howto <- Back to the HOWTO section]