summaryrefslogtreecommitdiff
path: root/devel/libtool
diff options
context:
space:
mode:
authortv <tv@pkgsrc.org>2006-03-02 18:50:17 +0000
committertv <tv@pkgsrc.org>2006-03-02 18:50:17 +0000
commit0c02ccfe23509ecaf627103365aa1bc44745b2ef (patch)
tree45c75e63309b3e3325f2cc29e99147d6df33d0d8 /devel/libtool
parent2ced427a2b2a3da475084c79bdec3ff93a3b8979 (diff)
downloadpkgsrc-0c02ccfe23509ecaf627103365aa1bc44745b2ef.tar.gz
Clarify the fact that libtool.m4 has no automatic patch, and the reasons
why there must not be such a patch.
Diffstat (limited to 'devel/libtool')
-rw-r--r--devel/libtool/patches/manual.README8
1 files changed, 5 insertions, 3 deletions
diff --git a/devel/libtool/patches/manual.README b/devel/libtool/patches/manual.README
index 0119b5d721e..81dc80357d4 100644
--- a/devel/libtool/patches/manual.README
+++ b/devel/libtool/patches/manual.README
@@ -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 @@ used to generate libtool's own "configure" scripts.
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:
=====