From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: install-html and install-pdf improvements
Date: Fri, 17 Apr 2009 18:18:00 -0000 [thread overview]
Message-ID: <83bpqvjg96.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0904171527200.7832@digraph.polyomino.org.uk>
> Date: Fri, 17 Apr 2009 15:30:08 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> cc: gdb-patches@sourceware.org
>
> On Fri, 17 Apr 2009, Eli Zaretskii wrote:
>
> > Yes, but I don't understand why did you need to define docdir in
> > addition to pdfdir and htmldir. Unlike the other two, docdir is not
> > used anywhere, so why define it?
>
> The default definitions of htmldir and pdfdir use ${docdir}
Sorry, I'm not following: what default definitions? These variables
are used neither in your patch nor in the current doc/Makefile.in.
What am I missing?
> (When the src repository moves to newer
> autoconf with native support for all these directory variables, the custom
> configure code to deal with them will go away, and the makefiles will not
> need any changes as they will already define all required variables.)
Well, you are talking here about something I don't know anything
about. But we don't need to install today a change that will only be
needed at some future time.
next prev parent reply other threads:[~2009-04-17 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 11:47 Joseph S. Myers
2009-04-17 15:26 ` Eli Zaretskii
2009-04-17 15:30 ` Joseph S. Myers
2009-04-17 18:18 ` Eli Zaretskii [this message]
2009-04-17 19:43 ` Tom Tromey
2009-04-17 19:49 ` Joseph S. Myers
2009-04-18 7:31 ` Eli Zaretskii
2009-04-18 9:32 ` Joseph S. Myers
2009-04-20 19:51 ` Carlos O'Donell
2009-04-20 20:56 ` Eli Zaretskii
2009-04-21 12:45 ` Joseph S. Myers
2009-04-21 18:54 ` Eli Zaretskii
2009-04-17 15:58 ` Joseph S. Myers
2009-04-17 16:58 ` Tom Tromey
2009-04-17 17:31 ` Daniel Jacobowitz
2009-04-17 18:47 ` Tom Tromey
2009-04-17 19:16 ` Eli Zaretskii
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=83bpqvjg96.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
/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