Changes between Version 13 and Version 14 of howto/RunningMaster
- Timestamp:
- Feb 25, 2017, 3:53:52 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
howto/RunningMaster
v13 v14 1 1 [wiki:howto <- Back to the HOWTO section] 2 2 3 = How to run MacPorts from the Subversion trunk=3 = How to run MacPorts from Git master = 4 4 5 5 * Audience: Anyone who wants to test the latest features or not wait for an official release 6 * Requires: Subversion (easy with 10.5 and later, tricky with 10.4 since that creates a circular dependency)6 * Requires: Git 7 7 8 8 == Introduction == 9 9 10 There are times when some may want to run MacPorts from a version newer than the current stable release. Maybe there's a new feature that you'd like to use, or it fixes an issue you've encountered, or you just like to be on the cutting edge. This explains how to run completely from trunk, using only Subversionto keep MacPorts up to date.10 There are times when some may want to run MacPorts from a version newer than the current stable release. Maybe there's a new feature that you'd like to use, or it fixes an issue you've encountered, or you just like to be on the cutting edge. This explains how to run completely from master, using only Git to keep MacPorts up to date. 11 11 12 12 == Installation == 13 13 14 See the Guide section on [http ://guide.macports.org/#installing.macports.subversion installing from subversion]14 See the Guide section on [https://guide.macports.org/#installing.macports.git installing from git] 15 15 16 16 == Keeping Up to Date == 17 17 18 === ''' Subversionupdate''' ===18 === '''Git update''' === 19 19 20 20 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: 21 21 {{{ 22 svn update /opt/mports/trunk 22 cd /opt/mports/macports-base && git pull --rebase 23 23 }}} 24 You will not find {{{selfupdate}}} useful anymore because it will always see that you have a version newer than the latest released version of MacPorts, and will not update your base code. Instead you should {{{ svn update}}} as above and then repeat the steps listed in step 2 of the guide section linked to above.24 You will not find {{{selfupdate}}} useful anymore because it will always see that you have a version newer than the latest released version of MacPorts, and will not update your base code. Instead you should {{{git pull}}} as above and then repeat the steps listed in step 2 of the guide section linked to above. 25 25 26 26 == Using MacPorts == 27 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.27 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 [https://trac.macports.org/newticket report the bug] when it happens. 28 28 29 29 30 30 == See also == 31 31 32 Additional topics related to MacPorts and SVN:32 Additional topics related to MacPorts and Git: 33 33 34 * Creating and testing ports not yet submitted to MacPorts: [https://guide.macports.org/#development.local-repositories Local SVNdevelopment repository]34 * Creating and testing ports not yet submitted to MacPorts: [https://guide.macports.org/#development.local-repositories Local Git development repository] 35 35 36 * [wiki:SyncingWithSVN Syncing the ports tree with SVN] rather than rsync. 37 36 * [wiki:SyncingWithGit Syncing the ports tree with Git] rather than rsync.