<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[126075] trunk/doc-new/guide/xml</title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta">
<dt>Revision</dt> <dd><a href="https://trac.macports.org/changeset/126075">126075</a></dd>
<dt>Author</dt> <dd>khindenburg@macports.org</dd>
<dt>Date</dt> <dd>2014-10-02 20:55:07 -0700 (Thu, 02 Oct 2014)</dd>
</dl>
<h3>Log Message</h3>
<pre>guide: fix spelling errors</pre>
<h3>Modified Paths</h3>
<ul>
<li><a href="#trunkdocnewguidexmlinstallingxml">trunk/doc-new/guide/xml/installing.xml</a></li>
<li><a href="#trunkdocnewguidexmlinternalsxml">trunk/doc-new/guide/xml/internals.xml</a></li>
<li><a href="#trunkdocnewguidexmlmacportsconfxml">trunk/doc-new/guide/xml/macports.conf.xml</a></li>
<li><a href="#trunkdocnewguidexmlportfiledependenciesxml">trunk/doc-new/guide/xml/portfile-dependencies.xml</a></li>
<li><a href="#trunkdocnewguidexmlportfilekeywordsxml">trunk/doc-new/guide/xml/portfile-keywords.xml</a></li>
<li><a href="#trunkdocnewguidexmlportfilevariantsxml">trunk/doc-new/guide/xml/portfile-variants.xml</a></li>
<li><a href="#trunkdocnewguidexmlportfiledevxml">trunk/doc-new/guide/xml/portfiledev.xml</a></li>
<li><a href="#trunkdocnewguidexmlprojectxml">trunk/doc-new/guide/xml/project.xml</a></li>
<li><a href="#trunkdocnewguidexmlusingxml">trunk/doc-new/guide/xml/using.xml</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="trunkdocnewguidexmlinstallingxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/installing.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/installing.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/installing.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -447,7 +447,7 @@
</span><span class="cx"> path for locating system executables (rsync, tar, etc.) during port installation, see the
</span><span class="cx"> <link linkend="internals.configuration-files.macports-conf">macports.conf</link> file
</span><span class="cx"> variable <varname>binpath</varname>. But changing this variable is for advanced users only,
</span><del>- and is not generally needed or recomended.</para>
</del><ins>+ and is not generally needed or recommended.</para>
</ins><span class="cx"> </note>
</span><span class="cx"> </listitem>
</span><span class="cx">
</span></span></pre></div>
<a id="trunkdocnewguidexmlinternalsxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/internals.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/internals.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/internals.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -321,7 +321,7 @@
</span><span class="cx"> stored in a single file named <filename>registry.db</filename>, although
</span><span class="cx"> the additional directory <filename>portfiles</filename> is used
</span><span class="cx"> temporarily for extracting stored Portfiles from the registry.
</span><del>- Futhermore, access to the registry may be locked using the
</del><ins>+ Furthermore, access to the registry may be locked using the
</ins><span class="cx"> <filename>.registry.lock</filename> file with the
</span><span class="cx"> <computeroutput>registry::exclusive_lock</computeroutput> and
</span><span class="cx"> <computeroutput>registry::exclusive_unlock</computeroutput> APIs.</para>
</span></span></pre></div>
<a id="trunkdocnewguidexmlmacportsconfxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/macports.conf.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/macports.conf.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/macports.conf.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -433,7 +433,7 @@
</span><span class="cx"> <title>variants.conf</title>
</span><span class="cx">
</span><span class="cx"> <para>This optional file specifies any variants you'd like to be invoked
</span><del>- globally. If a variant specified ib this file is not supported by a given
</del><ins>+ globally. If a variant specified in this file is not supported by a given
</ins><span class="cx"> Portfile, the variant is simply ignored.</para>
</span><span class="cx">
</span><span class="cx"> <para>Default: none</para>
</span></span></pre></div>
<a id="trunkdocnewguidexmlportfiledependenciesxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/portfile-dependencies.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/portfile-dependencies.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/portfile-dependencies.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -138,7 +138,7 @@
</span><span class="cx"> <para>File dependencies should only be used if one of the reasons listed
</span><span class="cx"> above applies. There are three types: <option>bin</option> for
</span><span class="cx"> programs, <option>lib</option> for libraries, and <option>path</option>
</span><del>- for any installed file. File dependencies are specifed in the form:
</del><ins>+ for any installed file. File dependencies are specified in the form:
</ins><span class="cx"> <replaceable>&lt;type&gt;</replaceable>:<replaceable>&lt;filespec&gt;</replaceable>:<replaceable>&lt;port&gt;</replaceable>.</para>
</span><span class="cx">
</span><span class="cx"> <para>For <option>bin</option> dependencies,
</span></span></pre></div>
<a id="trunkdocnewguidexmlportfilekeywordsxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/portfile-keywords.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/portfile-keywords.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/portfile-keywords.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -110,9 +110,9 @@
</span><span class="cx"> <listitem>
</span><span class="cx"> <para>A port's maintainers are the people who have agreed to take
</span><span class="cx"> responsibility for keeping the port up-to-date. Most ports have only a
</span><del>- single maintainer, but some ports have two or more comaintainers. The
</del><ins>+ single maintainer, but some ports have two or more co-maintainers. The
</ins><span class="cx"> <literal>maintainers</literal> keyword lists the maintainers' email
</span><del>- addresses, preferrably in the obfuscated form which hides them
</del><ins>+ addresses, preferably in the obfuscated form which hides them
</ins><span class="cx"> from spambots:</para>
</span><span class="cx">
</span><span class="cx"> <itemizedlist>
</span></span></pre></div>
<a id="trunkdocnewguidexmlportfilevariantsxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/portfile-variants.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/portfile-variants.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/portfile-variants.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -144,7 +144,7 @@
</span><span class="cx">
</span><span class="cx"> <para>Variant descriptions are strings, so one should take care not to put
</span><span class="cx"> whitespace between the brackets and the beginning and end of the variant
</span><del>- description, and also not to use unnceccessary whitespace, unlike with
</del><ins>+ description, and also not to use unnecessary whitespace, unlike with
</ins><span class="cx"> port descriptions and long_descriptions.</para>
</span><span class="cx"> </section>
</span><span class="cx">
</span></span></pre></div>
<a id="trunkdocnewguidexmlportfiledevxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/portfiledev.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/portfiledev.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/portfiledev.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -196,7 +196,7 @@
</span><span class="cx"> <para>A port's maintainers are the people who have agreed to take
</span><span class="cx"> responsibility for keeping the port up-to-date. The
</span><span class="cx"> <literal>maintainers</literal> keyword lists the maintainers' email
</span><del>- addresses, preferrably in the obfuscated form which hides them
</del><ins>+ addresses, preferably in the obfuscated form which hides them
</ins><span class="cx"> from spambots. For more, see the full explanation of the <link
</span><span class="cx"> linkend="reference.keywords.maintainers">maintainers keyword</link> in
</span><span class="cx"> the <link linkend="reference.keywords">Global Keywords</link> section
</span></span></pre></div>
<a id="trunkdocnewguidexmlprojectxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/project.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/project.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/project.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -51,7 +51,7 @@
</span><span class="cx"> <itemizedlist>
</span><span class="cx"> <listitem><para>using the search bar that appears on each page</para></listitem>
</span><span class="cx"> <listitem><para>using <ulink url="https://trac.macports.org/search?portsummarysearch=on">the search page</ulink></para></listitem>
</span><del>- <listitem><para>browsing the list of <ulink url="https://trac.macports.org/report">categorised reports</ulink></para></listitem>
</del><ins>+ <listitem><para>browsing the list of <ulink url="https://trac.macports.org/report">categorized reports</ulink></para></listitem>
</ins><span class="cx"> <listitem><para>making an advanced search by constructing a <ulink url="https://trac.macports.org/query">custom query</ulink></para></listitem>
</span><span class="cx"> </itemizedlist>
</span><span class="cx"> </para>
</span><span class="lines">@@ -300,7 +300,7 @@
</span><span class="cx"> the email address of the port's maintainer (use <command>port info
</span><span class="cx"> &lt;portname&gt;</command> to find this). If multiple maintainers
</span><span class="cx"> are listed, enter the first maintainer's email address here and
</span><del>- enter the remainining maintainers' email addresses in the
</del><ins>+ enter the remaining maintainers' email addresses in the
</ins><span class="cx"> <guimenu>Cc</guimenu> field. Exclude the email address
</span><span class="cx"> <email>openmaintainer@macports.org</email> if it appears.
</span><span class="cx"> If the maintainer's email address is
</span><span class="lines">@@ -469,7 +469,7 @@
</span><span class="cx"> <listitem>
</span><span class="cx"> <para>An account in the <ulink
</span><span class="cx"> url="https://trac.macports.org/">MacPorts Trac</ulink>,
</span><del>- preferrably with the email address you want to use for your
</del><ins>+ preferably with the email address you want to use for your
</ins><span class="cx"> port.</para>
</span><span class="cx"> </listitem>
</span><span class="cx"> <listitem>
</span><span class="lines">@@ -487,7 +487,7 @@
</span><span class="cx"> would like to encourage you to apply after a few months.</para>
</span><span class="cx"> </listitem>
</span><span class="cx"> <listitem>
</span><del>- <para>Expert knowldge of the software you want to maintain or
</del><ins>+ <para>Expert knowledge of the software you want to maintain or
</ins><span class="cx"> experience in <filename>Portfile</filename> programming. You can
</span><span class="cx"> pick those up along the way. Your knowledge about the software
</span><span class="cx"> you want to maintain is probably more than what most other
</span></span></pre></div>
<a id="trunkdocnewguidexmlusingxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/using.xml (126074 => 126075)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/using.xml 2014-10-03 03:28:38 UTC (rev 126074)
+++ trunk/doc-new/guide/xml/using.xml 2014-10-03 03:55:07 UTC (rev 126075)
</span><span class="lines">@@ -76,7 +76,7 @@
</span><span class="cx">
</span><span class="cx"> <programlisting><prompt>$</prompt> <userinput>sudo port -d selfupdate</userinput></programlisting>
</span><span class="cx">
</span><del>- <para>The output may give you an idea why the build failed. Look for the first occurances of
</del><ins>+ <para>The output may give you an idea why the build failed. Look for the first occurrences of
</ins><span class="cx"> <quote>error</quote>. If you cannot figure out what's wrong yourself, feel free to ask on the
</span><span class="cx"> <email>macports-users@lists.macosforge.org</email> mailing list and attach the output generated by
</span><span class="cx"> <command>sudo port -d selfupdate</command>.</para>
</span><span class="lines">@@ -98,7 +98,7 @@
</span><span class="cx">
</span><span class="cx"> <para>The <option>sync</option> action performs a subset of <option>selfupdate</option>. It synchronizes the
</span><span class="cx"> ports tree, as does <option>selfupdate</option>, but it does not check for MacPorts upgrades. On OS X,
</span><del>- unless there is a special reason not to do so, you should alawys run <link
</del><ins>+ unless there is a special reason not to do so, you should always run <link
</ins><span class="cx"> linkend="using.port.selfupdate">selfupdate</link>.</para>
</span><span class="cx">
</span><span class="cx"> <para><option>sync</option> does not accept any switches.</para>
</span><span class="lines">@@ -122,7 +122,7 @@
</span><span class="cx"> </variablelist>
</span><span class="cx">
</span><span class="cx"> <note>
</span><del>- <para>This command will only be availible in MacPorts version 2.4 and above.</para>
</del><ins>+ <para>This command will only be available in MacPorts version 2.4 and above.</para>
</ins><span class="cx"> </note>
</span><span class="cx"> </section>
</span><span class="cx">
</span><span class="lines">@@ -135,7 +135,7 @@
</span><span class="cx"> <para><option>reclaim</option> does not accept any switches.</para>
</span><span class="cx">
</span><span class="cx"> <note>
</span><del>- <para> This command will only be availible in MacPorts version 2.4 and above.</para>
</del><ins>+ <para> This command will only be available in MacPorts version 2.4 and above.</para>
</ins><span class="cx"> </note>
</span><span class="cx"> </section>
</span><span class="cx">
</span><span class="lines">@@ -683,7 +683,7 @@
</span><span class="cx">
</span><span class="cx"> <programlisting><prompt>$ </prompt><userinput>port -q contents <varname>&lt;portname&gt;</varname> | grep -E '/s?bin/'</userinput></programlisting>
</span><span class="cx">
</span><del>- <para>The <option>-q</option> (quiet) flag supresses the header line in this case, but is not strictly necessary.</para>
</del><ins>+ <para>The <option>-q</option> (quiet) flag suppresses the header line in this case, but is not strictly necessary.</para>
</ins><span class="cx">
</span><span class="cx"> <para><option>contents</option> accepts:</para>
</span><span class="cx">
</span><span class="lines">@@ -1025,7 +1025,7 @@
</span><span class="cx"> <title>Invoking Variants</title>
</span><span class="cx">
</span><span class="cx"> <para>A variant can only be invoked when a port is installed. After you have determined what variants
</span><del>- a given port has, if any, you may install a port using the variant by specifying its name preceeded by
</del><ins>+ a given port has, if any, you may install a port using the variant by specifying its name preceded by
</ins><span class="cx"> a plus or minus sign on the command line, for example</para>
</span><span class="cx">
</span><span class="cx"> <programlisting><prompt>$ </prompt><userinput>sudo port install apache2 +openldap</userinput></programlisting>
</span></span></pre>
</div>
</div>
</body>
</html>