From: Jim Blandy <jimb@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] doc/Makefile.in install
Date: Fri, 22 Nov 2002 12:37:00 -0000 [thread overview]
Message-ID: <vt2wun51hm5.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <15838.36534.883345.847460@localhost.redhat.com>
Elena Zannoni <ezannoni@redhat.com> writes:
> 'make install' in the doc directory wasn't doing anything useful....
>
> Is this ok? (lifted from bfd/doc's makefile)
>
> Elena
>
>
> 2002-11-22 Elena Zannoni <ezannoni@redhat.com>
>
> * Makefile.in (install): Make install do some real work.
>
> Index: Makefile.in
> ===================================================================
> RCS file: /cvs/uberbaum/gdb/doc/Makefile.in,v
> retrieving revision 1.23
> diff -u -p -r1.23 Makefile.in
> --- Makefile.in 20 Nov 2002 00:47:59 -0000 1.23
> +++ Makefile.in 22 Nov 2002 20:10:08 -0000
> @@ -134,7 +134,7 @@ STABS_DOC_FILES = \
> #### Host, target, and site specific Makefile fragments come in here.
> ###
>
> -all install:
> +all:
>
> info: $(INFO_DEPS)
> dvi: gdb.dvi gdbint.dvi stabs.dvi refcard.dvi
> @@ -432,3 +432,4 @@ distclean: clean
> maintainer-clean realclean: distclean
> rm -f GDBvn.texi *.info* *.dvi *.ps *.html *.pdf
>
> +install: install-info
I think, at some point in the distant past, it was controversial
whether packages should install their info files by default. I think
that was back when disks were much smaller than they are now.
Nowadays most packages install their info by default, so there's no
reason for GDB not to do so as well.
next prev parent reply other threads:[~2002-11-22 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 12:12 Elena Zannoni
2002-11-22 12:37 ` Jim Blandy [this message]
2002-11-22 13:02 ` Elena Zannoni
2002-11-22 14:16 ` Andrew Cagney
2002-11-22 15:58 ` Elena Zannoni
2002-11-22 17:42 ` Elena Zannoni
2002-11-25 13:32 ` Andrew Cagney
2002-11-25 22:15 ` Eli Zaretskii
2002-11-26 14:45 ` Elena Zannoni
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=vt2wun51hm5.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.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