unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: INSTALL-CVS
Date: Mon, 02 Jun 2003 12:56:30 -0400	[thread overview]
Message-ID: <200306021656.h52GuUxg016120@rum.cs.yale.edu> (raw)
In-Reply-To: 8582-Mon02Jun2003070602+0300-eliz@elta.co.il

> That's because in the normal (non-CVS) build, the files in the info
> directory are already there.
> 
> Sorry, I forgot all those gory details.  The _real_ answer to your
> question is that (1) "make bootstrap" builds the Info manuals,
> and (2) if you build the CVS without bootstrapping, "make instal"
> will make sure the Info manuals are up to date, and if not rebuild
> them (see the target install-arch-indep which depends on info).

I have changed my Makefile.in long ago to add `man' to the default
target.  The only cases where it might hurt is if the Emacs tarball
comes with Texinfo files more recent than the Info files (that would
be a bug in the tarball) or if the program that untars the tarball
does not obey the timestamps in the tarball and happens to untar
the Texinfo files after untarring the Ifno files.

Maybe we can avoid all this by using two different Makefile.in
depending on whether it's checked out via CVS or taken from a tarball.
I.e. the `make-dist' script would slightly adjust the Makefile.in by
removing the `man' target from the default target.


	Stefan

  reply	other threads:[~2003-06-02 16:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 21:31 INSTALL-CVS Nick Roberts
2003-06-01 15:24 ` INSTALL-CVS Eli Zaretskii
2003-06-01 20:51   ` INSTALL-CVS Nick Roberts
2003-06-02  4:06     ` INSTALL-CVS Eli Zaretskii
2003-06-02 16:56       ` Stefan Monnier [this message]
2003-06-02 22:34         ` INSTALL-CVS Nick Roberts
2003-06-02 22:35       ` INSTALL-CVS Nick Roberts
2003-06-03  4:06     ` INSTALL-CVS Richard Stallman
2003-06-03  6:54       ` INSTALL-CVS David Masterson
2003-06-04 11:38         ` INSTALL-CVS Andreas Schwab
2003-06-04 14:42           ` INSTALL-CVS Stefan Monnier
2003-06-04 17:26             ` INSTALL-CVS David Masterson
2003-06-04 17:27               ` INSTALL-CVS Stefan Monnier
2003-06-04 17:52                 ` INSTALL-CVS David Masterson
2003-06-04 17:55                   ` INSTALL-CVS Stefan Monnier
2003-06-05 10:58             ` INSTALL-CVS Richard Stallman
2003-06-05 14:02               ` INSTALL-CVS Stefan Monnier
2003-06-05 19:02                 ` INSTALL-CVS Nick Roberts
2003-06-06 17:02                 ` INSTALL-CVS Richard Stallman
2003-06-04 17:38           ` INSTALL-CVS David Masterson
2003-06-04 18:06             ` INSTALL-CVS Stefan Monnier
2003-06-04 20:54               ` INSTALL-CVS David Masterson
2003-06-04 21:00                 ` INSTALL-CVS Stefan Monnier
2003-06-04 23:01                   ` INSTALL-CVS David Masterson
2003-06-05 21:46                   ` INSTALL-CVS Richard Stallman
2003-06-05 23:38                     ` INSTALL-CVS David Masterson
2003-06-05 12:49                 ` INSTALL-CVS Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2002-06-16 18:41 INSTALL-CVS D. Goel
2002-06-16 19:02 ` INSTALL-CVS Simon Josefsson
2002-06-17  6:07   ` INSTALL-CVS Eli Zaretskii
2002-06-18 16:29     ` INSTALL-CVS D. Goel
2002-06-19  5:15       ` INSTALL-CVS 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200306021656.h52GuUxg016120@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).