[26521] trunk/doc/guide/xml/portfiles/quick.xml

[source_changes at macosforge.org]

Revision: 26521
          http://trac.macosforge.org/projects/macports/changeset/26521
Author:   jmpp at macports.org
Date:     2007-06-27 09:35:33 -0700 (Wed, 27 Jun 2007)

Log Message:
-----------

Advice on setting appropriate permissions on the ${prefix}/var/macports/{distfiles,build} dirs for quick testing a still in development Portfile.
Thanks to Brian Campbell <lambda at continuation.org> for the patch! Closes #12187.

Also make it clear that you only need -d to debug the testing, not -v *and* -d.

Modified Paths:
--------------
    trunk/doc/guide/xml/portfiles/quick.xml

Modified: trunk/doc/guide/xml/portfiles/quick.xml
===================================================================
--- trunk/doc/guide/xml/portfiles/quick.xml	2007-06-27 16:23:31 UTC (rev 26520)
+++ trunk/doc/guide/xml/portfiles/quick.xml	2007-06-27 16:35:33 UTC (rev 26521)
@@ -36,12 +36,28 @@
       MacPorts</link> sections of this guide describes the process in
       detail. </para>
 
+    <para>In order for these commands to work, you're going to need
+      permission to write to certain areas of your MacPorts tree. You
+      need to be able to write
+      to <filename>${prefix}/var/macports/build</filename> and
+      <filename>${prefix}/var/macports/distfiles</filename>. You
+      could run all of these commands as a superuser (prefix the
+      commands with <command>sudo</command>), but you might
+      accidentally install a broken package that way, or otherwise
+      damage up your MacPorts installation. Another option is to change
+      the owner of just those directories to your user, so you can
+      write to those directories but not your whole
+      <filename>${prefix}</filename> tree. To do this,
+      run <userinput>chown username
+      ${prefix}/var/macports/build</userinput> and <userinput>chown
+      -R username ${prefix}/var/macports/distfiles</userinput>.</para>
+
     <para>Since you're interested in writing a
       <filename>Portfile</filename>, you should invoke the
-      <command>port</command> with the <option>-v</option> (verbose
-      output) and the <option>-d</option> (debugging option) switches.
-      This will display useful messages that are usually suppressed
+      <command>port</command> with the <option>-d</option> (debugging option)
+      switch. This will display useful messages that are usually suppressed
       while running MacPorts.</para>
+
   </sect1>
 
   <sect1 id="basics">

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