[105007] trunk/doc-new/guide/xml/using.xml

[afb at macports.org]

Revision: 105007
          https://trac.macports.org/changeset/105007
Author:   afb at macports.org
Date:     2013-04-07 08:03:21 -0700 (Sun, 07 Apr 2013)
Log Message:
-----------
Document where the .rpm packages end up

Modified Paths:
--------------
    trunk/doc-new/guide/xml/using.xml

Modified: trunk/doc-new/guide/xml/using.xml
===================================================================
--- trunk/doc-new/guide/xml/using.xml	2013-04-07 15:02:21 UTC (rev 105006)
+++ trunk/doc-new/guide/xml/using.xml	2013-04-07 15:03:21 UTC (rev 105007)
@@ -752,7 +752,7 @@
       <para>Binary packages are standalone binary installers that are
       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
+      Packages), or .rpm (RPM Package Manager) format. MacPorts may also
       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>
@@ -778,7 +778,12 @@
 
       <programlisting><prompt>%%</prompt> <userinput>sudo port rpm pstree</userinput></programlisting>
 
-      <para>All packages are placed in a port's work directory.</para>
+      <para>All packages are placed in a port's work directory,
+      except for rpms that are placed under the regular "RPMS":</para>
+
+      <programlisting><prompt>%%</prompt> <userinput>port work pstree</userinput></programlisting>
+      <programlisting><prompt>%%</prompt> <userinput>rpm --eval %{_rpmdir}</userinput></programlisting>
+
     </section>
   </section>
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20130407/fc893532/attachment-0001.html>