[29454] trunk/doc-new/guide/xml/portfiledev.xml
source_changes at macosforge.org
source_changes at macosforge.org
Sun Sep 23 16:07:25 PDT 2007
Revision: 29454
http://trac.macosforge.org/projects/macports/changeset/29454
Author: markd at macports.org
Date: 2007-09-23 16:07:24 -0700 (Sun, 23 Sep 2007)
Log Message:
-----------
Move the "local portfile repositories" section towards the end of the chapter because
it is a more natural place for it.
Modified Paths:
--------------
trunk/doc-new/guide/xml/portfiledev.xml
Modified: trunk/doc-new/guide/xml/portfiledev.xml
===================================================================
--- trunk/doc-new/guide/xml/portfiledev.xml 2007-09-23 22:55:16 UTC (rev 29453)
+++ trunk/doc-new/guide/xml/portfiledev.xml 2007-09-23 23:07:24 UTC (rev 29454)
@@ -78,78 +78,6 @@
</note>
</section>
- <section id="development.local-repositories">
- <title>Local Portfile Repositories</title>
-
- <para>To create and test Portfiles that are not yet committed to
- subversion, you may create a local Portfile repository as shown. Replace
- the hypothetical user <filename>julesverne</filename> with your username
- in the example below.</para>
-
- <orderedlist>
- <listitem>
- <para>Open the <filename>sources.conf</filename> file in a text
- editor.</para>
-
- <programlisting><prompt>%%</prompt> <userinput>cd ${prefix}/etc/macports/</userinput>
-<prompt>%%</prompt> <userinput>pico sources.conf</userinput></programlisting>
- </listitem>
-
- <listitem>
- <para>Insert a URL pointing to your local repository location before
- the rsync URL as shown.</para>
-
- <programlisting>file:///Users/julesverne/ports
-rsync://rsync.macports.org/release/ports
-</programlisting>
-
- <note>
- <para>The file URL should always appear before the rsync URL so that
- local Portfiles can be tested that are duplicated in the MacPorts
- tree, because the <command>port</command> command will always
- operate on the first Portfile it encounters.</para>
- </note>
- </listitem>
-
- <listitem>
- <para>Place the Portfiles you create inside a directory whose name
- matches the port, which should in turn be placed inside a directory
- that reflect the port's primary category (the first category entry in
- the Portfile).</para>
-
- <programlisting><prompt>%%</prompt> <userinput>cd /Users/julesverne</userinput>
-<prompt>%%</prompt> <userinput>mkdir -p ports/games/bestevergame</userinput>
-<prompt>%%</prompt> <userinput>cd ports/games/bestevergame</userinput>
-<prompt>%%</prompt> <userinput>touch Portfile</userinput></programlisting>
- </listitem>
-
- <listitem>
- <para>After a Portfile is created (see below), use the MacPorts
- <command>portindex</command> command in the local repository's
- directory to install it into the
- <filename>Portindex</filename>.</para>
-
- <programlisting>%% <userinput>cd /Users/julesverne/ports</userinput>
-%% <userinput>portindex</userinput></programlisting>
-
- <screen>Creating software index in /Users/julesverne/ports
-Adding port games/bestevergame
-
-Total number of ports parsed: 1
-Ports successfully parsed: 1
-Ports failed: 0</screen>
- </listitem>
- </orderedlist>
-
- <para>Once the local port is added to the <filename>Portindex</filename>,
- it becomes available for searching or installation as with any other
- Portfile in the MacPorts tree as shown.</para>
-
- <programlisting><prompt>%%</prompt> <userinput>port search bestever</userinput></programlisting>
-
- <screen>bestevergame games/bestevergame 1.1 The Best Ever Game</screen>
- </section>
-
<section id="development.creating-portfile">
<title>Creating a Portfile</title>
@@ -660,6 +588,78 @@
</section>
</section>
+ <section id="development.local-repositories">
+ <title>Local Portfile Repositories</title>
+
+ <para>To create and test Portfiles that are not yet committed to
+ subversion, you may create a local Portfile repository as shown. Replace
+ the hypothetical user <filename>julesverne</filename> with your username
+ in the example below.</para>
+
+ <orderedlist>
+ <listitem>
+ <para>Open the <filename>sources.conf</filename> file in a text
+ editor.</para>
+
+ <programlisting><prompt>%%</prompt> <userinput>cd ${prefix}/etc/macports/</userinput>
+<prompt>%%</prompt> <userinput>pico sources.conf</userinput></programlisting>
+ </listitem>
+
+ <listitem>
+ <para>Insert a URL pointing to your local repository location before
+ the rsync URL as shown.</para>
+
+ <programlisting>file:///Users/julesverne/ports
+rsync://rsync.macports.org/release/ports
+</programlisting>
+
+ <note>
+ <para>The file URL should always appear before the rsync URL so that
+ local Portfiles can be tested that are duplicated in the MacPorts
+ tree, because the <command>port</command> command will always
+ operate on the first Portfile it encounters.</para>
+ </note>
+ </listitem>
+
+ <listitem>
+ <para>Place the Portfiles you create inside a directory whose name
+ matches the port, which should in turn be placed inside a directory
+ that reflect the port's primary category (the first category entry in
+ the Portfile).</para>
+
+ <programlisting><prompt>%%</prompt> <userinput>cd /Users/julesverne</userinput>
+<prompt>%%</prompt> <userinput>mkdir -p ports/games/bestevergame</userinput>
+<prompt>%%</prompt> <userinput>cd ports/games/bestevergame</userinput>
+<prompt>%%</prompt> <userinput>touch Portfile</userinput></programlisting>
+ </listitem>
+
+ <listitem>
+ <para>After a Portfile is created (see below), use the MacPorts
+ <command>portindex</command> command in the local repository's
+ directory to install it into the
+ <filename>Portindex</filename>.</para>
+
+ <programlisting>%% <userinput>cd /Users/julesverne/ports</userinput>
+%% <userinput>portindex</userinput></programlisting>
+
+ <screen>Creating software index in /Users/julesverne/ports
+Adding port games/bestevergame
+
+Total number of ports parsed: 1
+Ports successfully parsed: 1
+Ports failed: 0</screen>
+ </listitem>
+ </orderedlist>
+
+ <para>Once the local port is added to the <filename>Portindex</filename>,
+ it becomes available for searching or installation as with any other
+ Portfile in the MacPorts tree as shown.</para>
+
+ <programlisting><prompt>%%</prompt> <userinput>port search bestever</userinput></programlisting>
+
+ <screen>bestevergame games/bestevergame 1.1 The Best Ever Game</screen>
+ </section>
+
<section id="development.practices">
<title>Portfile Best Practices</title>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20070923/08623f60/attachment.html
More information about the macports-changes
mailing list