<pre style='margin:0'>
Rainer Müller (raimue) pushed a commit to branch master
in repository macports-guide.
</pre>
<p><a href="https://github.com/macports/macports-guide/commit/5ea520a904ebce864ec5a7e0a335f9dbdfd4cf83">https://github.com/macports/macports-guide/commit/5ea520a904ebce864ec5a7e0a335f9dbdfd4cf83</a></p>
<pre style="white-space: pre; background: #F8F8F8"><span style='display:block; white-space:pre;color:#808000;'>commit 5ea520a904ebce864ec5a7e0a335f9dbdfd4cf83
</span>Author: Rainer Müller <raimue@macports.org>
AuthorDate: Mon Apr 23 17:42:34 2018 +0200
<span style='display:block; white-space:pre;color:#404040;'> adoc: Regenerate *.adoc with docbookrx
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> 'make guide-fromadoc' is now working and produces HTML.
</span>---
guide/adoc/portfile-phase.adoc | 6 +-
guide/adoc/project.adoc | 128 ++++++++++++++++++++---------------------
2 files changed, 67 insertions(+), 67 deletions(-)
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/guide/adoc/portfile-phase.adoc b/guide/adoc/portfile-phase.adoc
</span><span style='display:block; white-space:pre;color:#808080;'>index a5a5e0c..e73ef3a 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/guide/adoc/portfile-phase.adoc
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/guide/adoc/portfile-phase.adoc
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -96,9 +96,9 @@ Instead, use ``depends_lib-append``.
</span> +
When a variant requires more or fewer dependencies, distfiles, or patchfiles, when the variant is invoked you want to add or remove items to the appropriate keyword values list set in the global section of the Portfile.
Use the appropriate keywords, for example:
<span style='display:block; white-space:pre;background:#ffe0e0;'>-** `depends_lib-append` or `depends_lib-delete```depends_lib-replace``
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** `distfiles-append` or `distfiles-delete```distfiles-replace``
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** `patchfiles-append` or `patchfiles-delete```patchfiles-replace``
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** `depends_lib-append` or `depends_lib-delete` or `depends_lib-replace`
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** `distfiles-append` or `distfiles-delete` or `distfiles-replace`
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** `patchfiles-append` or `patchfiles-delete` or `patchfiles-replace`
</span>
[[_reference.phases.installation.argument_modifiers]]
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/guide/adoc/project.adoc b/guide/adoc/project.adoc
</span><span style='display:block; white-space:pre;color:#808080;'>index d447e8a..1ffb68f 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/guide/adoc/project.adoc
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/guide/adoc/project.adoc
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -51,7 +51,7 @@ Upgrading a single port can lead to software errors in other ports that have not
</span>
Once you are logged into Trac, you may click link:New Ticket and you will be presented with a new ticket window shown in the graphic below.
Follow the Trac ticket guidelines below to fill out the form.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-If you are reporting a failed port install and a log was mentioned in the error, please use the [label]#I have files to attach to this ticket# checkbox to add that log file to the ticket.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+If you are reporting a failed port install and a log was mentioned in the error, please use the *>I have files to attach to this ticket* checkbox to add that log file to the ticket.
</span> // <screenshot>
// <info>
// <title>A new Trac ticket</title>
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -83,7 +83,7 @@ Please see below for longer and more detailed explanations.
</span> | Content
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Summary#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Summary**
</span> |
[replaceable]``$port``[replaceable]``$version``[replaceable]``[$variants]``: [replaceable]``short
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -91,7 +91,7 @@ Please see below for longer and more detailed explanations.
</span>
*Example:* openssl @1.0.1e_1+universal: DTLS handshake error messages with openconnect
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Description#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Description**
</span> |
Describe your problem. Preformatted text (such as terminal
output) should be put in ``{{{[replaceable]``three curly
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -99,86 +99,86 @@ Please see below for longer and more detailed explanations.
</span> amounts of output rather than pasting. Use the preview
button!
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Type#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Type**
</span> |
// <tbody>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>defect</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>defect</emphasis></entry>
</span> // <entry>Bugs, build failures, documentation fixes</entry>
// </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>enhancement</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>enhancement</emphasis></entry>
</span> // <entry>Improving existing work</entry>
// </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>update</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>update</emphasis></entry>
</span> // <entry>Update requests or patch submissions for ports</entry>
// </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>submissions</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>submissions</emphasis></entry>
</span> // <entry>Submission of new <filename>Portfile</filename>s</entry>
// </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>request</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>request</emphasis></entry>
</span> // <entry>Requests for new ports</entry>
// </row>
// </tbody>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Priority#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Priority**
</span> |
<span style='display:block; white-space:pre;background:#ffe0e0;'>- Use menu:normal[] or menu:low[]. menu:High[] is reserved for MacPorts developers.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Use *>normal* or **>low**. *>High* is reserved for MacPorts developers.
</span>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Milestone#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Milestone**
</span> |Leave empty.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Component#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Component**
</span> |
// <tbody>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>base</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>base</emphasis></entry>
</span> // <entry>Tickets affecting MacPorts itself</entry>
// </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>guide</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>guide</emphasis></entry>
</span> // <entry>Use for documentation</entry>
// </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>ports</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>ports</emphasis></entry>
</span> // <entry>Tickets affecting specific ports. Remember to set
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// the <guilabel>port</guilabel> field!</entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// the <emphasis role="strong">>port</emphasis> field!</entry>
</span> // </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>server/hosting</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>server/hosting</emphasis></entry>
</span> // <entry>Use for infrastructure issues</entry>
// </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>website</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>website</emphasis></entry>
</span> // <entry>Enhancements and fixes for the web site</entry>
// </row>
// <row>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-// <entry><guimenu>wiki</guimenu></entry>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+// <entry><emphasis role="strong">>wiki</emphasis></entry>
</span> // <entry>Enhancements and fixes for the wiki (or just edit
// it directly!)</entry>
// </row>
// </tbody>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Version#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Version**
</span> |The version of MacPorts you are running.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Keywords#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Keywords**
</span> |``maintainer`` if you are the port's
maintainer. `haspatch` if you are attaching
a patch. link:Full
list.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Port#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Port**
</span> |The name of the port affected by this ticket. Separate
multiple using spaces. Leave empty for non-port
tickets.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-|[label]#Owner#/[label]#Cc#
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+|**>Owner**/**>Cc**
</span> |Full email address or GitHub username of the port's
maintainer. Run `port info --maintainer [replaceable]``<portname>``` to
look this up. Do not add
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -186,16 +186,16 @@ Please see below for longer and more detailed explanations.
</span> or
// <email>openmaintainer@macports.org</email>
$$.$$ For ports with
<span style='display:block; white-space:pre;background:#ffe0e0;'>- multiple maintainers, only put the first maintainer into the [label]#Owner# field and all others in the [label]#Cc# field. You do not need to Cc
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ multiple maintainers, only put the first maintainer into the *>Owner* field and all others in the *>Cc* field. You do not need to Cc
</span> yourself.
|===
====
There are certain conventions used to ensure that Trac tickets convey as much accurate information as possible so problems and contributions may be acted upon efficiently.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Summary:#[replaceable]``[port]``[replaceable]``[version]``[replaceable]``[concise description]``
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Summary:*[replaceable]``[port]``[replaceable]``[version]``[replaceable]``[concise description]``
</span> ** Example: "rrdtool @1.2.23 +python Configure error - build failure"
<span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Description:# All details that might be relevant to someone reading the ticket. Be sure to mention the versions of your operating system and Xcode install. link:Wiki formatting should be used to ensure that text is formatted correctly. Use the Preview button before submitting. If you want to post preformatted text such as a log or terminal output, make sure you use `{{{[replaceable]``$$...$$``}}}` around the text or it could break the page layout. Example:
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Description:* All details that might be relevant to someone reading the ticket. Be sure to mention the versions of your operating system and Xcode install. link:Wiki formatting should be used to ensure that text is formatted correctly. Use the Preview button before submitting. If you want to post preformatted text such as a log or terminal output, make sure you use `{{{[replaceable]``$$...$$``}}}` around the text or it could break the page layout. Example:
</span>
....
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -208,38 +208,38 @@ Submitters are advised to trim inline pastes and logs to what's really relevant
</span> Long output, such as the full log from a port build, should be added as an attachment, not pasted inline.
See [label]#I have files to attach to this
ticket# below.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Type:# There are five types of tickets.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:defect[] - The default; any port/MacPorts build/runtime failures and/or documentation corrections.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:enhancement[] - Tickets, with or without patches, created to enhance something that isn't failing its intended purpose.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:update[] - Tickets, with or without patches, involving updating a port to a newer upstream version.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:submission[] - Tickets created to submit Portfiles for software not currently available in MacPorts.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:request[] - Tickets created to request the creation of a new port.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Priority:# Assign a priority level to the ticket.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:High[] - Reserved for the use of MacPorts team members, as they are the best fit to determine which reports warrant a higher priority over others.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:Normal[] - The default. For normal port failures, non-critical enhancement requests, non-critical port failures.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:Low[] - For mostly cosmetic improvements, documentation corrections/improvements, etc.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:Not set[] - Anything that doesn't fit the categories high, normal, or low.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Milestone:# Leave this blank. MacPorts developers will set this to the version of MacPorts that contains a fix for the ticket when they commit a change. Note that this is only meaningful for changes in MacPorts itself, since changes to ports are continuously provided to users. If the milestone is [label]#MacPorts Future# no version of MacPorts with the fix has been released yet.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Component:# Set what part of the MacPorts Project the ticket is to be filed against.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:base[] - Tickets related to MacPorts base code.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:guide[] - Documentation enhancements and error corrections, or patches to the MacPorts Guide.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:ports[] - Tickets related to ports.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:server/hosting[] - For MacPorts hosting & server-side issues.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:website[] - MacPorts website enhancements and error corrections.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-** menu:wiki[] - MacPorts Wiki enhancements and error corrections.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Version:# Select the MacPorts version you are using when it is applicable.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Keywords:# Type any keywords that might help when searching for tickets. It is not useful to list words here that already appear elsewhere in the ticket. Keywords also serve as tags; for example, use "`tiger`" if reporting a bug that only affects Mac OS X 10.4, "`haspatch`" if a fix is attached to the ticket, "`maintainer`" if you are the port's maintainer, or "`LP64`" if reporting an issue that only affects 64-bit platforms.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Type:* There are five types of tickets.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>defect* - The default; any port/MacPorts build/runtime failures and/or documentation corrections.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>enhancement* - Tickets, with or without patches, created to enhance something that isn't failing its intended purpose.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>update* - Tickets, with or without patches, involving updating a port to a newer upstream version.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>submission* - Tickets created to submit Portfiles for software not currently available in MacPorts.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>request* - Tickets created to request the creation of a new port.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Priority:* Assign a priority level to the ticket.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>High* - Reserved for the use of MacPorts team members, as they are the best fit to determine which reports warrant a higher priority over others.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>Normal* - The default. For normal port failures, non-critical enhancement requests, non-critical port failures.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>Low* - For mostly cosmetic improvements, documentation corrections/improvements, etc.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>Not set* - Anything that doesn't fit the categories high, normal, or low.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Milestone:* Leave this blank. MacPorts developers will set this to the version of MacPorts that contains a fix for the ticket when they commit a change. Note that this is only meaningful for changes in MacPorts itself, since changes to ports are continuously provided to users. If the milestone is *>MacPorts Future* no version of MacPorts with the fix has been released yet.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Component:* Set what part of the MacPorts Project the ticket is to be filed against.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>base* - Tickets related to MacPorts base code.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>guide* - Documentation enhancements and error corrections, or patches to the MacPorts Guide.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>ports* - Tickets related to ports.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>server/hosting* - For MacPorts hosting & server-side issues.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>website* - MacPorts website enhancements and error corrections.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+** *>wiki* - MacPorts Wiki enhancements and error corrections.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Version:* Select the MacPorts version you are using when it is applicable.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Keywords:* Type any keywords that might help when searching for tickets. It is not useful to list words here that already appear elsewhere in the ticket. Keywords also serve as tags; for example, use "`tiger`" if reporting a bug that only affects Mac OS X 10.4, "`haspatch`" if a fix is attached to the ticket, "`maintainer`" if you are the port's maintainer, or "`LP64`" if reporting an issue that only affects 64-bit platforms.
</span> +
See link:the
TicketsKeywordGuidelines wiki page for a clickable list of all keywords.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Cc:# Anyone else besides the ticket reporter and assignee who would like to be kept involved in the development of the ticket. Multiple email addresses or GitHub usernames should be separated with a comma and a space (e.g., ``neverpanic, you@example.org, maintainer@macports.org``).
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Cc:* Anyone else besides the ticket reporter and assignee who would like to be kept involved in the development of the ticket. Multiple email addresses or GitHub usernames should be separated with a comma and a space (e.g., ``neverpanic, you@example.org, maintainer@macports.org``).
</span> +
<span style='display:block; white-space:pre;background:#ffe0e0;'>-When reporting port-related tickets, make sure you add the port maintainers email address or GitHub username to the [label]#Cc:# field so they are notified of the ticket (unless you have commit access, then see [label]#Assign
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+When reporting port-related tickets, make sure you add the port maintainers email address or GitHub username to the *>Cc:* field so they are notified of the ticket (unless you have commit access, then see [label]#Assign
</span> To:# below). You can obtain the email address or GitHub username of the port maintainer by running `port info
--maintainers [replaceable]``[port]```
<span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Assign To:# Only users with commit access can edit this field. If this is not you, see the section on the menu:Cc[] field above.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Assign To:* Only users with commit access can edit this field. If this is not you, see the section on the *>Cc* field above.
</span> +
<span style='display:block; white-space:pre;background:#ffe0e0;'>-For tickets on ports, enter the email address or GitHub username of the port's maintainer (use `port info [replaceable]``[port]``` to find this). If multiple maintainers are listed, enter the first maintainer's email address or GitHub username here and enter the remaining maintainers' email addresses or GitHub usernames in the menu:Cc[] field.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+For tickets on ports, enter the email address or GitHub username of the port's maintainer (use `port info [replaceable]``[port]``` to find this). If multiple maintainers are listed, enter the first maintainer's email address or GitHub username here and enter the remaining maintainers' email addresses or GitHub usernames in the *>Cc* field.
</span> Exclude the email address
+
// <email>openmaintainer@macports.org</email>
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -247,8 +247,8 @@ Exclude the email address
</span> If the maintainer's email address is
// <email>nomaintainer@macports.org</email>
, leave the field blank.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#Port:# For tickets on ports, enter the name of the port (or ports, space-separated, when multiple are affected).
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* [label]#I have files to attach to this ticket:# Use this checkbox to attach files to the ticket immediately after you create it. Or you can attach files later using the [label]#Attach File# button.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>Port:* For tickets on ports, enter the name of the port (or ports, space-separated, when multiple are affected).
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* *>I have files to attach to this ticket:* Use this checkbox to attach files to the ticket immediately after you create it. Or you can attach files later using the *>Attach File* button.
</span> +
If the file you are attaching is larger than 256 KiB, please compress it with bzip2 or gzip first to save space on the server and bandwidth for those downloading it, as Trac will not preview files above that size anyway.
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -332,9 +332,9 @@ where `$portname` is the name of the port you are submitting.
</span> Please fix any warnings and errors.
. Either submit the new port through link:a pull request on GitHub...
. $$...$$or create a Trac ticket.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-.. Set the type to [label]#submission#.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-.. Set the component to [label]#ports#.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-.. Set the [label]#port# field to the name of the new port.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+.. Set the type to **>submission**.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+.. Set the component to **>ports**.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+.. Set the *>port* field to the name of the new port.
</span> .. Attach the [path]_Portfile_ and any required patchfiles to the ticket.
. If your ticket or pull request doesn't receive any attention within a few days you may send an email to
+
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -361,10 +361,10 @@ where `$portname` is the name of the port you modified.
</span> Please fix any warnings and errors before submitting your changes.
. Either submit the port update through link:a pull request on GitHub...
. $$...$$or create a Trac ticket.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-.. Set the type to [label]#enhancement# for miscellaneous enhancements, to [label]#defect# for bug fixes, or to [label]#update# for version updates.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-.. Set the component to [label]#ports#.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-.. Set the [label]#port# field to the name of the port you want to change.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-.. Put the maintainer's email address or GitHub username into the [label]#Cc# field. You can use
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+.. Set the type to *>enhancement* for miscellaneous enhancements, to *>defect* for bug fixes, or to *>update* for version updates.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+.. Set the component to **>ports**.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+.. Set the *>port* field to the name of the port you want to change.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+.. Put the maintainer's email address or GitHub username into the *>Cc* field. You can use
</span> +
[source]
----
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -514,8 +514,8 @@ If the build completes successfully, run `sudo
</span> in the directory where you edited the [path]_Portfile_.
You can inspect the generated unified diff in [path]_change-$portname-maintainer.diff_ if you want.
. If you are only changing the maintainer, link:file a pull request on GitHub.
<span style='display:block; white-space:pre;background:#ffe0e0;'>-. You may also link:file a new ticket in Trac to change the maintainer, though GitHub pull requests are preferred. Set [label]#type# to [label]#enhancement#. Leave the [label]#milestone# field empty. If you added yourself as co-maintainer, add the other maintainers in the [label]#Cc# field. Finally, fill in the [label]#port# field, set [label]#keywords# to `haspatch` (because you are attaching a patch), check the box that you want to attach files to the ticket and submit. After submissio [...]
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-. If you are also fixing a bug, make a separate commit for that in your pull request, or attach a separate patch for that change to the same ticket. If you are fixing a bug that already has a ticket, attach a patch fixing the bug there and file the maintainer change in a separate ticket (with a separate patch) as discussed above. In general, please create a separate patch for each semantic change. Doing so simplifies reviewing. It enables each independent change to be accepted without wo [...]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+. You may also link:file a new ticket in Trac to change the maintainer, though GitHub pull requests are preferred. Set *>type* to **>enhancement**. Leave the *>milestone* field empty. If you added yourself as co-maintainer, add the other maintainers in the *>Cc* field. Finally, fill in the *>port* field, set *>keywords* to `haspatch` (because you are attaching a patch), check the box that you want to attach files to the ticket and submit. After submission, attach the patch you created in [...]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+. If you are also fixing a bug, make a separate commit for that in your pull request, or attach a separate patch for that change to the same ticket. If you are fixing a bug that already has a ticket, attach a patch fixing the bug there and file the maintainer change in a separate ticket (with a separate patch) as discussed above. In general, please create a separate patch for each semantic change. Doing so simplifies reviewing. It enables each independent change to be accepted without wo [...]
</span> . If your pull request or ticket doesn't receive any attention within a few days you may send an email to
+
// <email>macports-dev@lists.macports.org</email>
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -575,7 +575,7 @@ A port may be considered abandoned if any of the following apply:
</span>
If you wish to initiate the Port Abandonment protocol and optionally volunteer as the new maintainer:
<span style='display:block; white-space:pre;background:#ffe0e0;'>-. File a new Trac ticket with the summary line: [Port Abandoned] [label]#portname#.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+. File a new Trac ticket with the summary line: [Port Abandoned] **>portname**.
</span> . The ticket should be assigned to the maintainer. Non-macports team members should Cc the maintainer.
. Set the ticket Type to Defect.
. In the Description field, refer to any unacknowledged ticket(s).
</pre><pre style='margin:0'>
</pre>