Wed Jan 23 13:46:22 2008 UTC ()
Explicitly mention that the PKGREVISION must be incremented when a
dependency of the package changes. I still have problems with some
packages that depend on GConf2, which doesn't exist anymore. The
dependency has silently changed to GConf, without increasing any
PKGREVISION. Same for gnome-vfs2 and gnome-vfs.


(rillig)
diff -r1.91 -r1.92 pkgsrc/doc/guide/files/fixes.xml
cvs diff -r1.91 -r1.92 pkgsrc/doc/guide/files/fixes.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/fixes.xml 2007/10/17 14:08:02 1.91
+++ pkgsrc/doc/guide/files/fixes.xml 2008/01/23 13:46:21 1.92
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: fixes.xml,v 1.91 2007/10/17 14:08:02 kano Exp $ --> 1<!-- $NetBSD: fixes.xml,v 1.92 2008/01/23 13:46:21 rillig Exp $ -->
2 2
3<chapter id="fixes"> <?dbhtml filename="fixes.html"?> 3<chapter id="fixes"> <?dbhtml filename="fixes.html"?>
4<title>Making your package work</title> 4<title>Making your package work</title>
5 5
6<sect1 id="general-operation"> 6<sect1 id="general-operation">
7 <title>General operation</title> 7 <title>General operation</title>
8 8
9 <sect2 id="portability-of-packages"> 9 <sect2 id="portability-of-packages">
10 <title>Portability of packages</title> 10 <title>Portability of packages</title>
11 11
12 <para>One appealing feature of pkgsrc is that it runs on many 12 <para>One appealing feature of pkgsrc is that it runs on many
13 different platforms. As a result, it is important to ensure, 13 different platforms. As a result, it is important to ensure,
14 where possible, that packages in pkgsrc are portable. This 14 where possible, that packages in pkgsrc are portable. This
@@ -589,26 +589,27 @@ DISTNAME= foo-17.43 @@ -589,26 +589,27 @@ DISTNAME= foo-17.43
589 <para>Changing <varname>HOMEPAGE</varname>, <varname>MAINTAINER</varname>, 589 <para>Changing <varname>HOMEPAGE</varname>, <varname>MAINTAINER</varname>,
590 or comments in Makefile.</para></listitem><listitem><para> 590 or comments in Makefile.</para></listitem><listitem><para>
591 Changing build variables if the resulting binary package is the same.</para></listitem><listitem><para> 591 Changing build variables if the resulting binary package is the same.</para></listitem><listitem><para>
592 Changing <filename>DESCR</filename>.</para></listitem><listitem><para> 592 Changing <filename>DESCR</filename>.</para></listitem><listitem><para>
593 Adding <varname>PKG_OPTIONS</varname> if the default options don't change.</para></listitem> 593 Adding <varname>PKG_OPTIONS</varname> if the default options don't change.</para></listitem>
594 </itemizedlist> 594 </itemizedlist>
595 595
596 <para>Examples of changes that do merit an increase to 596 <para>Examples of changes that do merit an increase to
597 <varname>PKGREVISION</varname> include:</para> 597 <varname>PKGREVISION</varname> include:</para>
598 <itemizedlist><listitem><para> 598 <itemizedlist><listitem><para>
599 Security fixes</para></listitem><listitem><para> 599 Security fixes</para></listitem><listitem><para>
600 Changes or additions to a patch file</para></listitem><listitem><para> 600 Changes or additions to a patch file</para></listitem><listitem><para>
601 Changes to the <filename>PLIST</filename></para></listitem> 601 Changes to the <filename>PLIST</filename></para></listitem>
 602 <listitem><para>A dependency is changed or renamed.</para></listitem>
602 </itemizedlist> 603 </itemizedlist>
603 604
604 <para>PKGREVISION must also be incremented when dependencies have ABI 605 <para>PKGREVISION must also be incremented when dependencies have ABI
605 changes.</para> 606 changes.</para>
606 </sect2> 607 </sect2>
607 608
608 <sect2 id="fixes.subst"> 609 <sect2 id="fixes.subst">
609 <title>Substituting variable text in the package files (the SUBST framework)</title> 610 <title>Substituting variable text in the package files (the SUBST framework)</title>
610 611
611 <para>When you want to replace the same text in multiple files 612 <para>When you want to replace the same text in multiple files
612 or when the replacement text varies, patches alone cannot help. 613 or when the replacement text varies, patches alone cannot help.
613 This is where the SUBST framework comes in. It provides an 614 This is where the SUBST framework comes in. It provides an
614 easy-to-use interface for replacing text in files. 615 easy-to-use interface for replacing text in files.