<pre style='margin:0'>
Rainer Müller (raimue) pushed a commit to branch master
in repository macports-guide.
</pre>
<p><a href="https://github.com/macports/macports-guide/commit/0c2ec9911bf44db4dabf7b8b162d0ba9f1026969">https://github.com/macports/macports-guide/commit/0c2ec9911bf44db4dabf7b8b162d0ba9f1026969</a></p>
<pre style="white-space: pre; background: #F8F8F8"><span style='display:block; white-space:pre;color:#808000;'>commit 0c2ec9911bf44db4dabf7b8b162d0ba9f1026969
</span>Author: Rainer Müller <raimue@macports.org>
AuthorDate: Wed Nov 16 20:16:30 2016 +0100
<span style='display:block; white-space:pre;color:#404040;'> Move paragraph on Portfile compatibility
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> It does not make sense to tell people on the very beginning of the
</span><span style='display:block; white-space:pre;color:#404040;'> installation instructions. Also, it is not really that important that it
</span><span style='display:block; white-space:pre;color:#404040;'> would need a colored box.
</span>---
guide/xml/installing.xml | 11 ++++-------
1 file changed, 4 insertions(+), 7 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 246ad46..f8b3727 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;'>@@ -148,13 +148,6 @@
</span> MacPorts on another OS platform, you must <link linkend="installing.macports.source">install MacPorts from
the source code</link>.</para>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <note>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- <para>Though a distinction is made between pre-release and release versions of MacPorts base, the ports
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- collection supports no such distinction or versioning. The <link
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- linkend="using.port.selfupdate">selfupdate</link> command installs the latest port revisions from
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- Subversion (at a slight delay), and updates MacPorts base to the latest released version.</para>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- </note>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-
</span> <section id="installing.macports.binary">
<title>OS X Package Install</title>
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -274,6 +267,10 @@
</span> you just like to be on the cutting edge. These steps explain how to run completely from trunk, using
only Subversion to keep MacPorts up to date.</para>
<span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Though a distinction is made between pre-release and release versions of MacPorts base, the ports
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ collection supports no such distinction or versioning. The <link linkend="using.port.selfupdate">selfupdate</link>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ command installs the latest ports tree, and updates MacPorts base to the latest released version.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span> <orderedlist>
<listitem>
<para>Check out MacPorts source</para>
</pre><pre style='margin:0'>
</pre>