unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: jmarant@nerim.net, emacs-devel@gnu.org
Subject: Re: [patch] leim/Makefile.in: make distclean should make clean
Date: Mon, 16 Feb 2004 20:42:57 +0900 (JST)	[thread overview]
Message-ID: <200402161142.UAA18057@etlken.m17n.org> (raw)
In-Reply-To: <2914-Mon16Feb2004113906+0200-eliz@elta.co.il>

In article <2914-Mon16Feb2004113906+0200-eliz@elta.co.il>, "Eli Zaretskii" <eliz@elta.co.il> writes:
>>  > make distclean in leim/Makefile.in doesn't currently make clean.
>>  > I've attached a patch.
>>  
>>  Thank you, I've just installed it.

> I'm not sure we should install that change as it is: it will cause
> "make distclean" to remove some of the files that are distributed as
> part of the Leim tarball.  For example, cyrillic.elc is removed by
> "make clean", but it is also part of leim-NN.MM.tar.gz, AFAICS.  And
> there are others.

?? Do we still make the Leim tarball?

> Perhaps the `clean' target needs to be changed as well.

I see your point.  The target clean is documented as this in
top Makefile.in. 

### `clean'
###      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.

It seems that distclean also should not delete *.elc.  About
maintainer-clean and extraclean, I'm not sure if we should
delete *.elc or not.  As they don't delete lisp/*.elc,
perhaps, it is better not to delete leim/*/*.elc.

Then, only the case that we should delete leim/*/*.elc is at
bootstrapping time.  Is it right?

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

  reply	other threads:[~2004-02-16 11:42 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 [this message]
2004-02-16 16:25       ` Eli Zaretskii
2004-02-16 16:57         ` Stefan Monnier
2004-02-16 23:25           ` Kenichi Handa
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

  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=200402161142.UAA18057@etlken.m17n.org \
    --to=handa@m17n.org \
    --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 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).