all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: eliz@elta.co.il, jmarant@nerim.net, emacs-devel@gnu.org
Subject: Re: [patch] leim/Makefile.in: make distclean should make clean
Date: Tue, 17 Feb 2004 08:25:41 +0900 (JST)	[thread overview]
Message-ID: <200402162325.IAA19109@etlken.m17n.org> (raw)
In-Reply-To: <jwv4qtrdl17.fsf-monnier+emacs/devel@asado.iro.umontreal.ca> (message from Stefan Monnier on 16 Feb 2004 11:57:51 -0500)

In article <jwv4qtrdl17.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>  At bootstrap we should delete *.elc and also those *.el files that
>>  were produced from *.tit and other files in *-DIC/ directories.

> [ I know it's not really related but anyway: ]

> Let me disagree here.  Removing those files in 99% of my cases does nothing
> better than significantly lengthen to time to get a working system.
> Yes, `bootstrap-clean' (which I'd call `spotless' or `cvsclean' since it's
> not only used for bootstrapping purposes) should remove those files, but
> not `bootstrap'.

> If people want to use `bootstrap' to get a "fully clean build", they should
> first do a `bootstrap-clean' explicitly.

But, there's no such target in ./Makefile.in (top level).
lisp/Makefile.in and nt/makefile.nt have it.
src/Makefile.in has "bootstrapclean" instead.  Do you mean
that we should add that target in ./Makefile.in.

In ./Makefile.in, we already have these targets.

# make clean  or  make mostlyclean
#      Delete all files from the current directory that are normally
#      created by building the program.	 Don't delete the files that
#      record the configuration.  Also preserve files that could be made
#      by building, but normally aren't because the distribution comes
#      with them.
#
#      Delete `.dvi' files here if they are not part of the distribution.
#
# make distclean
#      Delete all files from the current directory that are created by
#      configuring or building the program.  If you have unpacked the
#      source and built the program without creating any other files,
#      `make distclean' should leave only the files that were in the
#      distribution.
#
# make maintainer-clean
#      Delete everything from the current directory that can be
#      reconstructed with this Makefile.  This typically includes
#      everything deleted by distclean, plus more: C source files
#      produced by Bison, tags tables, info files, and so on.
#
# make extraclean
#      Still more severe - delete backup and autosave files, too.

It seems that maintainer-clean is the best target to make
the directory the same as just after we do "cvs co".

---
Ken'ichi HANDA
handa@m17n.org

  reply	other threads:[~2004-02-16 23:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 19:15 [patch] leim/Makefile.in: make distclean should make clean Jérôme Marant
2004-02-15 23:35 ` Kenichi Handa
2004-02-16  9:39   ` Eli Zaretskii
2004-02-16 11:42     ` Kenichi Handa
2004-02-16 16:25       ` Eli Zaretskii
2004-02-16 16:57         ` Stefan Monnier
2004-02-16 23:25           ` Kenichi Handa [this message]
2004-02-17  0:44             ` Stefan Monnier
2004-02-16 12:37     ` Jérôme Marant
2004-02-16 14:39       ` Stefan Monnier
2004-02-16 16:54         ` Jérôme Marant
2004-02-16 16:13       ` Eli Zaretskii
2004-02-16 17:07         ` Jérôme Marant
2004-02-16 19:54           ` Eli Zaretskii
2004-02-16 21:28             ` Jérôme Marant
2004-02-16 21:51               ` Jérôme Marant
2004-02-17  7:00               ` Eli Zaretskii
2004-02-17  8:13                 ` Jérôme Marant

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=200402162325.IAA19109@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=eliz@elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=jmarant@nerim.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.