<pre style='margin:0'>
Joshua Root (jmroot) pushed a commit to branch master
in repository macports-guide.

</pre>
<p><a href="https://github.com/macports/macports-guide/commit/ad21b68afefeedde63e29f73abf85716a51e8ee0">https://github.com/macports/macports-guide/commit/ad21b68afefeedde63e29f73abf85716a51e8ee0</a></p>
<pre style="white-space: pre; background: #F8F8F8">The following commit(s) were added to refs/heads/master by this push:
<span style='display:block; white-space:pre;color:#404040;'>     new ad21b68  Update subversion install instructions to git
</span>ad21b68 is described below

<span style='display:block; white-space:pre;color:#808000;'>commit ad21b68afefeedde63e29f73abf85716a51e8ee0
</span>Author: Joshua Root <jmr@macports.org>
AuthorDate: Sat Feb 25 14:36:48 2017 +1100

<span style='display:block; white-space:pre;color:#404040;'>    Update subversion install instructions to git
</span>---
 guide/xml/installing.xml | 39 ++++++++++++++++++---------------------
 1 file changed, 18 insertions(+), 21 deletions(-)

<span style='display:block; white-space:pre;color:#808080;'>diff --git a/guide/xml/installing.xml b/guide/xml/installing.xml
</span><span style='display:block; white-space:pre;color:#808080;'>index 7931820..eda69d2 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/guide/xml/installing.xml
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/guide/xml/installing.xml
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -255,17 +255,15 @@
</span>             </orderedlist>
         </section>
 
<span style='display:block; white-space:pre;background:#ffe0e0;'>-        <section id="installing.macports.subversion">
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-            <title>Subversion Install</title>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-            <?macro-outdated reason="after the move to Git and GitHub" ?>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+        <section id="installing.macports.git">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+            <title>Git Install</title>
</span> 
             <para>If you installed MacPorts using the package installer, skip this section.</para>
 
             <para>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
<span style='display:block; white-space:pre;background:#ffe0e0;'>-                you just like to be on the cutting edge. These steps explain how to run completely from trunk, using
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-                only Subversion to keep MacPorts up to date.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                you just like to be on the cutting edge. These steps explain how to run completely from master, using
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                only Git to keep MacPorts up to date.</para>
</span> 
             <para>Though a distinction is made between pre-release and release versions of MacPorts base, the ports
                 collection supports no such distinction or versioning. The <link linkend="using.port.selfupdate">selfupdate</link>
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -277,20 +275,13 @@
</span> 
                     <para>Pick a location to store a working copy of the MacPorts code. For this example,
                         <filename>/opt/mports</filename> will be used, but you can put the source anywhere. This example
<span style='display:block; white-space:pre;background:#ffe0e0;'>-                        will create <filename>/opt/mports/trunk</filename> containing everything needed for
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                        will create <filename>/opt/mports/macports-base</filename> containing everything needed for
</span>                         MacPorts.</para>
 
                     <programlisting><prompt>$</prompt> <userinput>mkdir -p /opt/mports</userinput>
 <!--                --><prompt>$</prompt> <userinput>cd /opt/mports</userinput>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-<!--                --><prompt>$</prompt> <userinput>svn checkout https://svn.macports.org/repository/macports/trunk</userinput></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!--                --><prompt>$</prompt> <userinput>git clone https://github.com/macports/macports-base.git</userinput></programlisting>
</span> 
<span style='display:block; white-space:pre;background:#ffe0e0;'>-                    <note>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-                        <para>You only really need the base subdirectory to run MacPorts, so you can avoid checking out
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-                            the rest if you don't want to use a Subversion-based ports tree (see Step 3 below). To just
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-                            get the base directory, append <filename>/base</filename> to the end of the svn checkout
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-                            command above. The resulting directory will then be
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-                            <filename>/opt/mports/base</filename>.</para>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-                    </note>
</span>                 </listitem>
 
                 <listitem>
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -300,7 +291,7 @@
</span>                         MacPorts to <filename>/opt/local</filename>. You can add <option>--prefix</option> to
                         <filename>./configure</filename> to relocate MacPorts to another directory if needed.</para>
 
<span style='display:block; white-space:pre;background:#ffe0e0;'>-                    <programlisting><prompt>$</prompt> <userinput>cd /opt/mports/trunk/base</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                    <programlisting><prompt>$</prompt> <userinput>cd /opt/mports/macports-base</userinput>
</span> <!--                --><prompt>$</prompt> <userinput>./configure --enable-readline</userinput>
 <!--                --><prompt>$</prompt> <userinput>make</userinput>
 <!--                --><prompt>$</prompt> <userinput>sudo make install</userinput>
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -308,19 +299,25 @@
</span>                 </listitem>
 
                 <listitem>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-                    <para>(Optional) Configure MacPorts to use port information from Subversion</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                    <para>(Optional) Configure MacPorts to use port information from Git</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                    <para>This step is useful if you want to do port development. Check out the ports tree from git:</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                    <programlisting><prompt>$</prompt> <userinput>cd /opt/mports</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!--                --><prompt>$</prompt> <userinput>git clone https://github.com/macports/macports-ports.git</userinput></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span> 
<span style='display:block; white-space:pre;background:#ffe0e0;'>-                    <para>This step is useful if you want to do port development. Open
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-                        <filename>/opt/local/etc/macports/sources.conf</filename> in a text editor. The last line which
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                    <para>Then open
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                        <filename>/opt/local/etc/macports/sources.conf</filename> in a text editor. The last line
</span>                         should look like this:</para>
 
                     <programlisting>rsync://rsync.macports.org/release/tarballs/ports.tar [default]</programlisting>
 
                     <para>Change it to point to the working copy you checked out:</para>
 
<span style='display:block; white-space:pre;background:#ffe0e0;'>-                    <programlisting>file:///opt/mports/trunk/dports [default]</programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                    <programlisting>file:///opt/mports/macports-ports [default]</programlisting>
</span> 
<span style='display:block; white-space:pre;background:#ffe0e0;'>-                    <para>Now MacPorts will look for portfiles in the working copy and use Subversion instead of rsync
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+                    <para>Now MacPorts will look for portfiles in the working copy and use Git instead of rsync
</span>                         to update your ports tree.</para>
                 </listitem>
 
</pre><pre style='margin:0'>

</pre>