[pkgsrc/trunk]: pkgsrc/devel/libtool/patches Clarify the fact that libtool.m4...

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/93dceae9b8cd
branches:  trunk
changeset: 509041:93dceae9b8cd
user:      tv <tv%pkgsrc.org@localhost>
date:      Thu Mar 02 18:50:17 2006 +0000

description:
Clarify the fact that libtool.m4 has no automatic patch, and the reasons
why there must not be such a patch.

diffstat:

 devel/libtool/patches/manual.README |  8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)

diffs (22 lines):

diff -r 3bc6cf87ec2c -r 93dceae9b8cd devel/libtool/patches/manual.README
--- a/devel/libtool/patches/manual.README       Thu Mar 02 18:46:16 2006 +0000
+++ b/devel/libtool/patches/manual.README       Thu Mar 02 18:50:17 2006 +0000
@@ -1,4 +1,4 @@
-$NetBSD: manual.README,v 1.8 2006/01/30 22:19:56 tv Exp $
+$NetBSD: manual.README,v 1.9 2006/03/02 18:50:17 tv Exp $
 
 ************************************************************************
 **** WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING ***
@@ -19,8 +19,10 @@
 
 These patches are not part of the automatic patches because libtool also
 installs these .m4 files at runtime, and we want the "off-the-shelf"
-versions of those files used instead.  So, when it comes time to update
-libtool, the following process should be used:
+versions of those files used instead -- we do NOT want the modified
+libtool.m4 copied into third party packages for reproducability and GPL
+reasons.  So, when it comes time to update libtool, the following process
+must be used:
 
 =====