From: Joel Brobecker <brobecker@adacore.com>
To: Brooks Moses <brooks@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [patch][gdb,etc] Add configure option to disable building internal documentation.
Date: Wed, 07 Nov 2007 20:52:00 -0000 [thread overview]
Message-ID: <20071107205234.GF3911@adacore.com> (raw)
In-Reply-To: <47321064.5040306@codesourcery.com>
> 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
next prev parent reply other threads:[~2007-11-07 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 23:18 Brooks Moses
2007-11-07 2:54 ` Daniel Jacobowitz
2007-11-07 4:10 ` Eli Zaretskii
2007-11-07 19:22 ` Brooks Moses
2007-11-07 20:52 ` Joel Brobecker [this message]
2007-11-07 22:22 ` Eli Zaretskii
2007-11-07 23:50 ` Mark Kettenis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071107205234.GF3911@adacore.com \
--to=brobecker@adacore.com \
--cc=brooks@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox