[wiki:howto <- Back to the HOWTO section]

= How to run MacPorts from Git master =

 * Audience: Anyone who wants to test the latest features or not wait for an official release
 * Requires: Git

== Introduction ==

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.

== Installation ==

See the Guide section on [https://guide.macports.org/#installing.macports.git installing from git]

== Keeping Up to Date ==

=== '''Git update''' ===

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/macports-base && git pull --rebase
}}}
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.

== 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 [https://trac.macports.org/newticket report the bug] when it happens.


== See also ==

Additional topics related to MacPorts and Git:

* Creating and testing ports not yet submitted to MacPorts: [https://guide.macports.org/#development.local-repositories Local Git development repository]

* [wiki:SyncingWithGit Syncing the ports tree with Git] rather than rsync.