<pre style='margin:0'>
Mojca Miklavec (mojca) pushed a commit to branch master
in repository macports-guide.
</pre>
<p><a href="https://github.com/macports/macports-guide/commit/32052defd5b32a0061a923475ea8f544eb9b28c2">https://github.com/macports/macports-guide/commit/32052defd5b32a0061a923475ea8f544eb9b28c2</a></p>
<pre style="white-space: pre; background: #F8F8F8">The following commit(s) were added to refs/heads/master by this push:
<span style='display:block; white-space:pre;color:#404040;'> new 32052de Add GitHub PortGroup doc, update directory listing
</span>32052de is described below
<span style='display:block; white-space:pre;color:#808000;'>commit 32052defd5b32a0061a923475ea8f544eb9b28c2
</span>Author: Enrico M. Crisostomo <enrico.m.crisostomo@gmail.com>
AuthorDate: Fri Dec 1 23:49:52 2017 +0100
<span style='display:block; white-space:pre;color:#404040;'> Add GitHub PortGroup doc, update directory listing
</span>---
guide/xml/portfileref.xml | 3 +
guide/xml/portgroup-github.xml | 198 +++++++++++++++++++++++++++++++++++++++++
guide/xml/portgroups.xml | 30 ++++---
3 files changed, 219 insertions(+), 12 deletions(-)
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/guide/xml/portfileref.xml b/guide/xml/portfileref.xml
</span><span style='display:block; white-space:pre;color:#808080;'>index 4f9a255..c68b788 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/guide/xml/portfileref.xml
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/guide/xml/portfileref.xml
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -38,6 +38,9 @@
</span> <xi:include href="portgroups.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<span style='display:block; white-space:pre;background:#e0ffe0;'>+ <xi:include href="portgroup-github.xml"
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ xmlns:xi="http://www.w3.org/2001/XInclude" />
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span> <xi:include href="portgroup-gnustep.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/guide/xml/portgroup-github.xml b/guide/xml/portgroup-github.xml
</span>new file mode 100644
<span style='display:block; white-space:pre;color:#808080;'>index 0000000..4566ce1
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>--- /dev/null
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/guide/xml/portgroup-github.xml
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -0,0 +1,198 @@
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<?xml version="1.0" encoding="UTF-8"?>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V5.0//EN"
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+"http://docbook.org/xml/5.0/dtd/docbook.dtd">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<section xml:id="reference.portgroup.github">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>PortGroup github</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>The <code>github</code> portgroup allows for efficient porting of
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ software hosted on GitHub.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <section xml:id="reference.portgroup.github.description">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>Description</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ This portgroup greatly simplifies the porting of software hosted on
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ GitHub. Provided a GitHub repository author follows common GitHub
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ practices, a port can be almost fully configured simply by declaring the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ repository coordinates. The <code>github</code> portgroup is indeed
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ capable of configuring, amongst other things:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <itemizedlist>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>The port <code>name</code>.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>The port <code>version</code>.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>The <code>distfiles</code> (if the project uses GitHub
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ releases).</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>The <code>livecheck</code> parameters.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </itemizedlist>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </section>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <section xml:id="reference.portgroup.github.setup">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>Setting up the GitHub repository coordinates</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ The main port configuration is triggered by the usage of the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <code>github.setup</code> keyword:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+PortGroup github 1.0
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+github.setup author project version [tag_prefix]</programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ By default, the port <code>name</code> will be set to the GitHub project
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ name (<code>project</code>) and <code>version</code> will be set to the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ GitHub project <code>version</code>. The port name can be overridden by
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ using the <code>name</code> keyword.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ The <code>tag_prefix</code> is optional, and it's used to specify a prefix
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ to use when constructing the tag name. If, for example, the project uses
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ tags such as <code>v1.0.0</code>, then the <code>tag_prefix</code> should
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ be set to <code>v</code>, as in the following example:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+github.setup author project version v</programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </section>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <section xml:id="reference.portgroup.github.distfilestrategy">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>Choosing a distfile strategy</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ GitHub, and as a consequence the <code>github</code> portgroup, offers
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ multiple mechanisms to get a distfile:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <itemizedlist>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Distfile from a <code>git</code> commit or tag.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Distfile from a GitHub <link
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ xlink:href="https://github.com/blog/1547-release-your-software">release</link>.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Distfile from a GitHub <link
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ xlink:href="https://github.com/blog/1302-goodbye-uploads">download</link>.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </listitem>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </itemizedlist>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ The default behaviour of the portgroup is using GitHub automatically
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ generated distfile from a <code>git</code> commit or tag. However, the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ best practice should be using a GitHub release.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </section>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <section xml:id="reference.portgroup.github.distfile">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>Distfile from tag or commit</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ The default behaviour of the <code>github</code> portgroup is leveraging
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ GitHub's ability to create a distfile from a <code>git</code> tag or
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ commit. In this case, the <code>distname</code> is irrelevant and should
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ not be set.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ If the project's developers do not tag their releases, they should be
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ encouraged to do so. Until they do, or in the case in which an untagged
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ development version has to be used, port maintainers have the possibility
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ of specifying a <code>git</code> commit hash and manually set the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <code>version</code> field. If the project does not assign version
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ numbers the port maintainer has to define one. Such versions typically
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ format the date of the chosen commit using the <code>YYYYMMDD</code>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ pattern. If, for example, the port maintainer decides to use a changeset
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ with the hash <code>0ff25277c3842598d919cd3c73d60768</code>, committed on
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ April 1, 2014, then the following would be used:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+github.setup someone someproject 0ff25277c3842598d919cd3c73d60768
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+version 20140401</programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </section>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <section xml:id="reference.portgroup.github.releases">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>Distfile from a GitHub release</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ The <code>github</code> portgroup allows maintainers to easily configure
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ the distfiles when the project uses GitHub releases. A release is the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ best distfile candidate, and project maintainers should be encouraged to
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ use them. To enable this feature, the following keyword must be used:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+github.tarball_from releases</programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ By default, the <code>github</code> portgroup sets <code>distname</code>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ to:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+distname ${github.project}-${github.version}</programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ However, GitHub does not enforce any rule for release distfiles, so port
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ maintainers may need to override the <code>distname</code> as they would
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ do for other ports.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </section>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <section xml:id="reference.portgroup.github.downloads">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>Distfile from a GitHub download</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Older projects use the discontinued <link
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ xlink:href="https://github.com/blog/1302-goodbye-uploads">downloads</link>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ service. New GitHub downloads can no longer be created, but old ones are
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ still available.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ If the project doesn't have GitHub releases but does have GitHub
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ downloads, they can be used using the following keyword:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+github.tarball_from downloads</programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Since GitHub doesn't enforce any naming rules for downloads, the portgroup
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ can only provide a sensible default value for <code>distname</code>, which
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ can be overridden if necessary.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </section>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <section xml:id="reference.portgroup.github.submodule">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>Using repositories with git submodules</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ If the project uses <code>git</code> submodules, some projects' tag- or
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ commit-based distfiles will not contain all the necessary files. Once
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ again, the best distfile candidate (if available) is a distfile from
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ GitHub releases, as described in the previous sections. However, in the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ case a project doesn't provide any other alternative, a project using
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ submodules can be successfully retrieved by fetching the sources using
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <code>git</code> and then using a <code>post-fetch</code> to initialize
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ the submodules:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+fetch.type git
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+post-fetch {
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ system -W ${worksrcpath} "git submodule update --init"
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+}</programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </section>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+</section>
</span><span style='display:block; white-space:pre;color:#808080;'>diff --git a/guide/xml/portgroups.xml b/guide/xml/portgroups.xml
</span><span style='display:block; white-space:pre;color:#808080;'>index b35eb23..e0ef3b7 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/guide/xml/portgroups.xml
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/guide/xml/portgroups.xml
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -10,27 +10,33 @@
</span> group of portfiles, in order that those portfiles can be expressed as simply as possible with
minimum redundancy.</para>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-<para>See the following folder for PortGroup definitions:</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>See the following folder for PortGroup definitions:</para>
</span> <para>
<filename>${prefix}/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/</filename>
</para>
<para>A sample listing follows:</para>
<para>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <programlisting><prompt>%%</prompt> <userinput>ls -1 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/</userinput></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><prompt>%%</prompt> <userinput>ls -1 /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/</userinput></programlisting>
</span>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <screen>archcheck-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <screen>active_variants-1.1.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+apache2-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+app-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+archcheck-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+bitbucket-1.0.tcl
</span> cmake-1.0.tcl
<span style='display:block; white-space:pre;background:#e0ffe0;'>+cmake-1.1.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+compiler_blacklist_versions-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+compilers-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+conflicts_build-1.0.tcl
</span> crossbinutils-1.0.tcl
<span style='display:block; white-space:pre;background:#ffe0e0;'>-gnustep-1.0.tcl
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-haskell-1.0.tcl
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-hocbinding-1.0.tcl
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-hunspelldict-1.0.tcl
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-kde4-1.0.tcl
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-kde4-1.1.tcl
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-.</screen>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+crossgcc-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+cxx11-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+cxx11-1.1.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+debug-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+elisp-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+github-1.0.tcl
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+...</screen>
</span> </para>
<para>The requirements of a minimum portfile using a portgroup varies by portgroup.
</pre><pre style='margin:0'>
</pre>