Strange file in Lispintro

Strange file in Lispintro

[Chong Yidong]

Is lispintro/Makefile.old really supposed to be in CVS?

Re: Strange file in Lispintro

[Eli Zaretskii]

> From: Chong Yidong <cyd@stupidchicken.com>
> Date: Sat, 18 Nov 2006 16:22:07 -0500
> 
> Is lispintro/Makefile.old really supposed to be in CVS?

It is no more strange than the other configury-related stuff in there:
aclocal.m4, configure.in, configure, and Makefile.am.  They are all
left-overs from when lispintro was a separate package.

Whether to keep them is up to Bob Chassel; I guess it depends on
whether the Lisp Intro needs ever to be distributed as a separate
package.

Re: Strange file in Lispintro

[Richard Stallman]

    It is no more strange than the other configury-related stuff in there:
    aclocal.m4, configure.in, configure, and Makefile.am.  They are all
    left-overs from when lispintro was a separate package.

    Whether to keep them is up to Bob Chassel; I guess it depends on
    whether the Lisp Intro needs ever to be distributed as a separate
    package.

Let's keep them in CVS just in case we ever want them again, but
make-dist should not put them in tarballs.

Re: Strange file in Lispintro

[Eli Zaretskii]

> From: Richard Stallman <rms@gnu.org>
> CC: cyd@stupidchicken.com, emacs-devel@gnu.org
> Date: Sun, 19 Nov 2006 02:59:02 -0500
> 
> Let's keep them in CVS just in case we ever want them again, but
> make-dist should not put them in tarballs.

make-dist already avoids putting those files in release tarballs.

Re: Strange file in Lispintro

[Glenn Morris]

Richard Stallman wrote:

>     It is no more strange than the other configury-related stuff in there:
>     aclocal.m4, configure.in, configure, and Makefile.am.
[...]
> Let's keep them in CVS just in case we ever want them again, but
> make-dist should not put them in tarballs.

These would seem to be ideal subjects for a "cvs remove", which puts
them in an Attic/ subdirectory. They would not appear in normal CVS
checkouts, but could still be recovered if necessary.

This has already been done with INSTALL and MANIFEST.