From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3170 invoked by alias); 7 Nov 2007 20:52:41 -0000 Received: (qmail 3159 invoked by uid 22791); 7 Nov 2007 20:52:41 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 07 Nov 2007 20:52:38 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E6E202AC283; Wed, 7 Nov 2007 15:52:36 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WEL4YZPRmidg; Wed, 7 Nov 2007 15:52:36 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id AEDB42AAA0C; Wed, 7 Nov 2007 15:52:36 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 8456DE7ACA; Wed, 7 Nov 2007 15:52:34 -0500 (EST) Date: Wed, 07 Nov 2007 20:52:00 -0000 From: Joel Brobecker To: Brooks Moses Cc: Eli Zaretskii , gdb-patches@sourceware.org Subject: Re: [patch][gdb,etc] Add configure option to disable building internal documentation. Message-ID: <20071107205234.GF3911@adacore.com> References: <4730F626.806@codesourcery.com> <47321064.5040306@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47321064.5040306@codesourcery.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-11/txt/msg00140.txt.bz2 > Anyhow, consider the viewpoint of a new end-user who has just installed > a binary package. For them, it's unlikely that the GDB documentation is > in /usr/local/info; it's probably going to be in /opt/$gdb-package/doc > or someplace. If that was set up with "make install-pdf", there will be > four or five manuals in there -- three of which are irrelevant to their > needs, and which they don't want. I agree that such an option would be very useful. I would even consider changing the default to not installing these docs unless an option is specified, since I think that most people who do gdb installs only care about building/installing/using. Even as a GDB developer who uses this documentation from time to time, I actually never look at the installed documentation, because I never do "make install"! Most of the time, I just go on the GDB webpage and browse the documentation from there. Anyway, I like the new option. Having the default one way or the other doesn't matter much to me, so don't let this prevent this idea from being implemented. We can always change the default later if we want to. That's the easy part. -- Joel