Page Menu
Home
FreeBSD
Search
Configure Global Search
Log In
Files
F147982255
D342.id581.diff
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Flag For Later
Award Token
Size
2 KB
Referenced Files
None
Subscribers
None
D342.id581.diff
View Options
Index: en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
===================================================================
--- en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
+++ en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
@@ -2719,19 +2719,35 @@
<!-- smiley-->
<emphasis>:-)</emphasis></para>
- <para>Note that only a single address without the comment part is
+ <para>Only a single address without the comment part is
allowed as a <varname>MAINTAINER</varname> value. The format
- used should be <literal>user@hostname.domain</literal>. Please
- do not include any descriptive text such as your real name in
- this entry—that merely confuses
- <filename>bsd.port.mk</filename>.</para>
+ used is <literal>user@hostname.domain</literal>. Please
+ do not include any descriptive text such as a real name in
+ this entry. That merely confuses the Ports infrastructure
+ and most tools using it.</para>
<para>The maintainer is responsible for keeping the port up to
- date, and ensuring the port works correctly. For a detailed
+ date and making sure that it works correctly. For a detailed
description of the responsibilities of a port maintainer, refer
- to the <link
+ to <link
xlink:href="&url.articles.contributing-ports;/maintain-port.html">The
- challenge for port maintainers</link> section.</para>
+ challenge for port maintainers</link>.</para>
+
+ <note>
+ <para>A maintainer volunteers to keep a port in good working
+ order. Maintainers have the primary responsibility for their
+ ports, but not exclusive ownership. Ports exist for the
+ benefit of the community and, in reality, belong to the
+ community. What this means is that people other than the
+ maintainer can make changes to a port. Large changes to the
+ Ports Collection might require changes to many ports. The
+ &os; Ports Management Team or members of other teams might
+ modify ports to fix dependency issues or other problems, like
+ a version bump for a shared library update. Some types of
+ fixes have <quote>blanket approval</quote>, allowing any
+ committer to fix those categories of problems on any
+ port.</para>
+ </note>
<para>Changes to the port will be sent to the maintainer of a port
for review and approval before being committed. If the
@@ -2748,7 +2764,8 @@
<para>We reserve the right to modify the maintainer's submission
to better match existing policies and style of the Ports
- Collection without explicit blessing from the submitter. Also,
+ Collection without explicit blessing from the submitter or the
+ maintainer. Also,
large infrastructural changes can result in a port being
modified without the maintainer's consent. These kinds of
changes will never affect the port's functionality.</para>
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Mon, Mar 16, 12:21 AM (16 m, 32 s)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
29743439
Default Alt Text
D342.id581.diff (2 KB)
Attached To
Mode
D342: Add a note about what a maintainer is not.
Attached
Detach File
Event Timeline
Log In to Comment