Revision: 105186
https://trac.macports.org/changeset/105186
Author: ryandesign at macports.org
Date: 2013-04-12 17:10:26 -0700 (Fri, 12 Apr 2013)
Log Message:
-----------
portfile-keywords.xml: clarify that comments can precede the PortSystem line, and that PortGroup lines can follow it. Mention the convention of changing "+" to "x" in port names.
Modified Paths:
--------------
trunk/doc-new/guide/xml/portfile-keywords.xml
Modified: trunk/doc-new/guide/xml/portfile-keywords.xml
===================================================================
--- trunk/doc-new/guide/xml/portfile-keywords.xml 2013-04-12 22:41:41 UTC (rev 105185)
+++ trunk/doc-new/guide/xml/portfile-keywords.xml 2013-04-13 00:10:26 UTC (rev 105186)
@@ -19,9 +19,10 @@
<term>PortSystem</term>
<listitem>
- <para>The top line of every Portfile; it must be followed by a blank
- line. It defines which version of the Portfile interpreter will be
- used.</para>
+ <para>The first non-comment line of every Portfile; it should be
+ followed by PortGroup inclusions (if any) and then a blank line.
+ It defines which version of the Portfile interpreter will be used.
+ (There is currently only one version.)</para>
<programlisting>PortSystem 1.0
@@ -35,7 +36,9 @@
<listitem>
<para>The name of the port. To avoid special interpretation by shells
and the like, names should contain only alphanumeric characters,
- underscores, dashes or dots.</para>
+ underscores, dashes or dots. For projects whose proper names contain
+ "+" characters, change these to "x" (i.e. "libstdc++" becomes
+ "libstdcxx").</para>
<programlisting>name foo</programlisting>
</listitem>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20130412/26ae07a8/attachment-0001.html>