[71187] trunk/doc-new/guide/xml/project.xml

[Ryan Schmidt]

On Sep 3, 2010, at 17:51, jmr at macports.org wrote:

> Revision: 71187
>          http://trac.macports.org/changeset/71187
> Author:   jmr at macports.org
> Date:     2010-09-03 15:51:03 -0700 (Fri, 03 Sep 2010)
> Log Message:
> -----------
> guide: use our standard version spec notation in the ticket summary line example
> 
> Modified Paths:
> --------------
>    trunk/doc-new/guide/xml/project.xml
> 
> Modified: trunk/doc-new/guide/xml/project.xml
> ===================================================================
> --- trunk/doc-new/guide/xml/project.xml	2010-09-03 22:38:17 UTC (rev 71186)
> +++ trunk/doc-new/guide/xml/project.xml	2010-09-03 22:51:03 UTC (rev 71187)
> @@ -104,7 +104,7 @@
> 
>           <itemizedlist>
>             <listitem>
> -              <para>Example: "rrdtool-1.2.23 Configure error - build
> +              <para>Example: "rrdtool @1.2.23 +python Configure error - build
>               failure"</para>
>             </listitem>
>           </itemizedlist>

Actually, this ticket summary suggestion, which many users follow when filing tickets, has always seemed like an oxymoron to me. Either there was a configure error, or there was a build failure; there can't have been both. Anyway, I would much rather the user use more specific ticket summary including the actual error message that occurred. Of course now that MacPorts 1.9 doesn't print any verbose output by default, many users are filing tickets with summaries letting us know that a shell command failed, which is of course completely useless information; we should specifically call out that users should not use ticket summaries that mention the shell command failing. We should explain to users that they should look in the log and find the relevant error message in there.