[31937] trunk/doc-new/guide/xml

ryandesign at macports.org ryandesign at macports.org
Wed Dec 12 04:03:06 PST 2007


Revision: 31937
          http://trac.macosforge.org/projects/macports/changeset/31937
Author:   ryandesign at macports.org
Date:     2007-12-12 04:03:01 -0800 (Wed, 12 Dec 2007)

Log Message:
-----------
doc-new: change 'OS X' to 'Mac OS X' because that's its correct name. Thanks to Anders for reminding me to fix this.

Modified Paths:
--------------
    trunk/doc-new/guide/xml/installing.xml
    trunk/doc-new/guide/xml/portfile-phase.7.xml
    trunk/doc-new/guide/xml/portfile-startupitem.7.xml
    trunk/doc-new/guide/xml/using.xml

Modified: trunk/doc-new/guide/xml/installing.xml
===================================================================
--- trunk/doc-new/guide/xml/installing.xml	2007-12-12 11:13:38 UTC (rev 31936)
+++ trunk/doc-new/guide/xml/installing.xml	2007-12-12 12:03:01 UTC (rev 31937)
@@ -17,7 +17,7 @@
     you don't plan to run X11 applications immediately. Apple's X11 is
     preferred over the MacPorts X11 port, and ports with an X11 dependency
     will be satisfied by Apple's X11. If Apple's X11 wasn't installed at the
-    same time the OS X was installed, follow these steps.</para>
+    same time Mac OS X was installed, follow these steps.</para>
 
     <orderedlist>
       <listitem>
@@ -41,7 +41,7 @@
       </listitem>
     </orderedlist>
 
-    <para>If you're using OS X 10.3 then you can download the X11 installer
+    <para>If you're using Mac OS X 10.3 then you can download the X11 installer
     from the Apple <ulink
     url="http://apple.com/support/downloads/x11formacosx.html">download
     page</ulink>.</para>
@@ -51,7 +51,7 @@
       apps. To verify the presence of both, check for files
       <filename>com.apple.pkg.X11User.bom</filename> &amp;
       <filename>com.apple.pkg.X11SDKLeo.bom</filename> in
-      <filename>/Library/Receipts/boms/</filename>. On OS X 10.4, look for
+      <filename>/Library/Receipts/boms/</filename>. On Mac OS X 10.4, look for
       files <filename>X11User.pkg</filename> &amp;
       <filename>X11SDK.pkg</filename> in
       <filename>/Library/Receipts/</filename>.</para>
@@ -102,7 +102,7 @@
       <listitem>
         <para>Download and install the latest version of <ulink
         url="http://developer.apple.com/tools/xcode/">Xcode Tools</ulink> from
-        Apple's developer site—do not install it from an OS X install disk
+        Apple's developer site—do not install it from a Mac OS X install disk
         unless you've already checked for a more recent version on Apple's
         site; older versions of Xcode Tools often cause port install
         failures.</para>
@@ -125,7 +125,7 @@
     </orderedlist>
 
     <note>
-      <para>Xcode Tools are not updated via OS X's Software Update
+      <para>Xcode Tools are not updated via Mac OS X's Software Update
       utility.</para>
     </note>
   </section>
@@ -133,8 +133,8 @@
   <section id="installing.macports">
     <title>Install MacPorts</title>
 
-    <para>If you are using OS X, you should install MacPorts using the OS X
-    package installer unless you do not wish to install it to
+    <para>If you are using Mac OS X, you should install MacPorts using the
+    Mac OS X package installer unless you do not wish to install it to
     <filename>/opt/local/</filename>, the default MacPorts location, or if you
     wish to install a pre-release version of MacPorts base. However, if you
     wish to install <ulink url="installing.source.multiple">multiple copies of
@@ -150,10 +150,10 @@
     </note>
 
     <section id="installing.binary">
-      <title>OS X Package Install</title>
+      <title>Mac OS X Package Install</title>
 
-      <para>To install MacPorts with the OS X package installer, follow these
-      steps.</para>
+      <para>To install MacPorts with the Mac OS X package installer, follow
+      these steps.</para>
 
       <orderedlist>
         <listitem>
@@ -247,7 +247,7 @@
   <section id="installing.shell">
     <title>Set the Bash Shell</title>
 
-    <para>The MacPorts installer (from OS X package or source) places a
+    <para>The MacPorts installer (from Mac OS X package or source) places a
     <filename>.profile</filename> file in your home directory (view files with
     a dot using <command>ls -a</command>). The contents of the
     <filename>~/.profile</filename> adds the MacPorts paths in front of the
@@ -312,4 +312,4 @@
     <link linkend="using.port.selfupdate">selfupdate</link> —one of several
     <link linkend="using.port">port commands</link>.</para>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>

Modified: trunk/doc-new/guide/xml/portfile-phase.7.xml
===================================================================
--- trunk/doc-new/guide/xml/portfile-phase.7.xml	2007-12-12 11:13:38 UTC (rev 31936)
+++ trunk/doc-new/guide/xml/portfile-phase.7.xml	2007-12-12 12:03:01 UTC (rev 31937)
@@ -1865,7 +1865,7 @@
     <section id="reference.phases.configure.universal">
       <title>Configure Universal</title>
 
-      <para>Universal keywords are used to make a port compile on the OS X
+      <para>Universal keywords are used to make a port compile on the Mac OS X
       platform to run on either PPC or Intel.</para>
 
       <note>
@@ -2558,4 +2558,4 @@
       </varlistentry>
     </variablelist>
   </section>
-</section>
\ No newline at end of file
+</section>

Modified: trunk/doc-new/guide/xml/portfile-startupitem.7.xml
===================================================================
--- trunk/doc-new/guide/xml/portfile-startupitem.7.xml	2007-12-12 11:13:38 UTC (rev 31936)
+++ trunk/doc-new/guide/xml/portfile-startupitem.7.xml	2007-12-12 12:03:01 UTC (rev 31937)
@@ -11,10 +11,10 @@
   listeners, etc. Ports that use StartupItem keywords create Mac OS X
   scripts for <ulink
   url="http://developer.apple.com/macosx/launchd.html">launchd</ulink>,
-  which is the Apple facility introduced with OS X 10.4 to replace xinetd
+  which is the Apple facility introduced with Mac OS X 10.4 to replace xinetd
   for starting and managing daemons. To support
   <command>launchd</command>, a program named <command>daemondo</command>
-  is provided by MacPorts base that serves as an adapter between OS X's
+  is provided by MacPorts base that serves as an adapter between Mac OS X's
   <command>launchd</command> and daemons (<quote>executable</quote>
   StartupItems) or traditional Unix startup scripts that start daemons
   (<quote>script</quote> StartupItems).</para>

Modified: trunk/doc-new/guide/xml/using.xml
===================================================================
--- trunk/doc-new/guide/xml/using.xml	2007-12-12 11:13:38 UTC (rev 31936)
+++ trunk/doc-new/guide/xml/using.xml	2007-12-12 12:03:01 UTC (rev 31937)
@@ -59,14 +59,14 @@
       <para>The <option>sync</option> option performs a subset of
       <option>selfupdate</option> actions. It synchronizes the ports tree, as
       does <option>selfupdate</option>, but it does not check for upgrades to
-      MacPorts base. On OS X, unless there is a special reason not to do so,
+      MacPorts base. On Mac OS X, unless there is a special reason not to do so,
       you should run <link
       linkend="using.port.selfupdate">selfupdate</link>.</para>
 
       <note>
-        <para>For platforms other than OS X, <option>sync</option> is the only
-        way to get port updates because <option>selfupdate</option> is
-        supported only on OS X.</para>
+        <para>For platforms other than Mac OS X, <option>sync</option> is the
+        only way to get port updates because <option>selfupdate</option> is
+        supported only on Mac OS X.</para>
       </note>
     </section>
 
@@ -457,13 +457,13 @@
       precompiled; they do not require MacPorts on the target system. Binary
       files created with MacPorts may be either .pkg (Mac OS X Installer
       Packages), or RPM (RPM Package Manager) format. MacPorts may also
-      process a .pkg package into an OS X .dmg disk image file. You may create
-      binary packages with the <command>port</command> command as shown in
-      these examples.</para>
+      process a .pkg package into a Mac OS X .dmg disk image file. You may
+      create binary packages with the <command>port</command> command as shown
+      in these examples.</para>
 
       <programlisting><prompt>%%</prompt> <userinput>port pkg pstree</userinput></programlisting>
 
-      <para>You may create an OS X .dmg disk image file as shown.</para>
+      <para>You may create a Mac OS X .dmg disk image file as shown.</para>
 
       <programlisting><prompt>%%</prompt> <userinput>port dmg pstree</userinput></programlisting>
 
@@ -599,4 +599,4 @@
     </section>
   </section>
 -->
-</chapter>
\ No newline at end of file
+</chapter>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20071212/751a70c5/attachment.html


More information about the macports-changes mailing list