From 7f08679de7a571feb0561978872f162f1af3b7c1 Mon Sep 17 00:00:00 2001
From: giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>
Date: Wed, 17 Feb 2010 03:35:50 +0000
Subject: Clarify pointlessness of merge build

git-svn-id: http://svn.code.sf.net/p/netpbm/code/trunk@1127 9d0c8265-081b-0410-96cb-a4ca84ce46f8
---
 doc/INSTALL | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/INSTALL b/doc/INSTALL
index 92e78540..ec2cfbed 100644
--- a/doc/INSTALL
+++ b/doc/INSTALL
@@ -261,6 +261,8 @@ make via the Configure dialog.
 
 The standard build is the conventional one.  The merge build is a way
 to reduce disk space and other resource usage in some configurations.
+These are rare configurations, mostly antique ones.  The advent of
+shared libraries largely obsoleted the merge build.
 
 In the standard build, hundreds of separate programs get built: ppmtogif,
 pamcomp, etc.
-- 
cgit 1.4.1