[pkgsrc/trunk]: pkgsrc/doc/guide/files In components, in patches section, add...

[gdt <gdt%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/e5c351bec129
branches:  trunk
changeset: 497804:e5c351bec129
user:      gdt <gdt%pkgsrc.org@localhost>
date:      Thu Aug 04 17:38:06 2005 +0000

description:
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.)

diffstat:

 doc/guide/files/components.xml |  8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diffs (22 lines):

diff -r 1919d9aba72e -r e5c351bec129 doc/guide/files/components.xml
--- a/doc/guide/files/components.xml    Thu Aug 04 16:54:53 2005 +0000
+++ b/doc/guide/files/components.xml    Thu Aug 04 17:38:06 2005 +0000
@@ -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 @@
       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>