all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org, sick_soul@yahoo.it
Subject: Re: dangerous command in Makefile.in uninstall rule
Date: Fri, 03 Mar 2006 14:35:22 +0200	[thread overview]
Message-ID: <u3bhz4sfp.fsf@gnu.org> (raw)
In-Reply-To: <E1FDs4z-0005Py-Ns@fencepost.gnu.org> (message from Richard Stallman on Mon, 27 Feb 2006 18:47:01 -0500)

> From: Richard Stallman <rms@gnu.org>
> Date: Mon, 27 Feb 2006 18:47:01 -0500
> Cc: bug-gnu-emacs@gnu.org
> 
>     $ rm -f cl* ada-mode*
>     autotype* calc* ccmode* ebrowse* efaq* eintr elisp*
>     eshell* eudc* idlwave* message* pcl-cvs* reftex*
>     speedbar* tramp* widget* woman* dired-x* ediff* emacs*
>     emacs-xtra* flymake* forms* gnus* info* mh-e*
>     newsticker* org* sc* ses* vip* smtpmail* url* rcirc*
>     erc*
> 
> We could make these more specific.  For instance, it could be
> 
> cl cl-*
> 
> or even
> 
> cl cl-[0-9] cl-[0-9][0-9]
> 
> for each one of the manuals.
> 
> But that is rather clumsy.  Is there any cleaner way to do it?

The cleanest way I know of is to have a single list of main Info files
(i.e., without the -[0-9] etc. suffixes, and then do something like
this:

   for f in ${INFO_FILES} do
     rm -f $$f $$f-[1-9] $$f-[1-9][0-9]
   done

We could then have the install target use INFO_FILES as well.

  parent reply	other threads:[~2006-03-03 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1FDKjh-0000YT-28@fencepost.gnu.org>
2006-02-27 12:45 ` dangerous command in Makefile.in uninstall rule Claudio Fontana
2006-02-27 23:47   ` Richard Stallman
2006-02-28 10:35     ` Claudio Fontana
2006-03-04 22:58       ` Karl Berry
2006-03-04 23:16         ` Claudio Fontana
2006-03-03 12:35     ` Eli Zaretskii [this message]
2006-03-04 13:37       ` Richard Stallman
2006-02-24 23:54 Claudio Fontana

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=u3bhz4sfp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=sick_soul@yahoo.it \
    /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.