Am Fre, 2002-06-07 um 17.23 schrieb Sam Liddicott:
>
>
> > -----Original Message-----
> > From: Akim Demaille [mailto:[EMAIL PROTECTED]]
> > Sent: 07 June 2002 16:06
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: cache directory is not removed
> >
> >
> > >>>>> "Sam" == Sam Steingold <[EMAIL PROTECTED]> writes:
> >
> > Sam> nope. when I distribute CLISP, I cannot assume that my users
> > Sam> have autoconf, so I distribute the generated configure scripts
> > Sam> too. i.e., the configure scripts are in the source tree and are
> > Sam> regenerated just before a release. thus, if I use autoconf 2.53,
> > Sam> I have to remove the cache directories by hand before a release,
> > Sam> so that they do not end up in the distribution file.
> >
> > But how do you write you dist target? How come it ends in the
> > tarball!?!
>
> I think this is a relavent question; you need to tweak your config files to
> stop this from being included in the make dist tar ball.
If using automake, "make dist" does not put autom4te.caches into the
tarball.
> Sadly *I* don't know how to do this, but it is the real answer,
If using automake, you don't have to do anything special.
> you are
> going to get lots of files created which aren't part of the distribution as
> time goes by
I you want to get rid of autom4te.cache, eg. because "make dist" doesn't
work for your package and because you are cutting tarballs with "tar czf
package.tar.gz packagedir, just add something similar to this to your
all toplevel Makefile.ams and run "make distclean" before the tar.
distclean-local:
rm -f autom4te.cache
Ralf
