summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorgdt <gdt@pkgsrc.org>2005-08-04 17:38:06 +0000
committergdt <gdt@pkgsrc.org>2005-08-04 17:38:06 +0000
commitef176f1a7ad869622cf594d7a1f644f1807febc9 (patch)
tree9485de981055ac0409d3b2ea9c7edbaed90d0a97
parent408cdaea6927d0e67e47a51f437f1c73b13808b9 (diff)
downloadpkgsrc-ef176f1a7ad869622cf594d7a1f644f1807febc9.tar.gz
In components, in patches section, add admonition to send patches that
are really fixes upstream. (Prompted by note back from an upstream maintainer after sending him someone else's bugfix patch that he hadn't already gotten asking me to make sure upstream maintainers get patches.)
-rw-r--r--doc/guide/files/components.xml8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/guide/files/components.xml b/doc/guide/files/components.xml
index 4f696bf5950..e12b833067b 100644
--- a/doc/guide/files/components.xml
+++ b/doc/guide/files/components.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: components.xml,v 1.11 2005/08/03 16:34:19 wiz Exp $ -->
+<!-- $NetBSD: components.xml,v 1.12 2005/08/04 17:38:06 gdt Exp $ -->
<chapter id="components"> <?dbhtml filename="components.html"?>
<title>Package components - files, directories and contents</title>
@@ -283,6 +283,12 @@ SITES_foo-file.tar.gz=http://www.somewhere.com/somehow/ \
for the patch files by using the <command>make makepatchsum</command>
command, see <xref linkend="components.distinfo"/>.</para>
+ <para>When adding a patch that corrects a problem in the distfile (rather
+ than e.g. enforcing pkgsrc's view of where man pages should go), send
+ the patch as a bug report to the maintainer. This benefits
+ non-pkgsrc users of the package, and usually enables removing
+ the patch in future version.</para>
+
<para>Patch files that are distributed by the author or other
maintainers can be listed in
<varname>$PATCHFILES</varname>. </para>