[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn copy conflicts with autotools ?

From: Henrique de Moraes Holschuh <hmh_at_debian.org>
Date: 2004-12-01 15:04:11 CET

On Wed, 01 Dec 2004, Eric PAIRE wrote:
> everything, but you have to make these generated files ignored to your
> versioning
> system, and there should be a way to remove them easily.

Maybe one of the automake targets do a full cleanup, I never tried to track
that down. I never needed it. When I need a thruly pristine tree, I just
export one from the revision control system, since *no* autogenerated files
are in there at all. Docs you don't want changing under your feet such as
COPYING are under version control, of course. But autotools do not touch
that if it is already in place, so I don't think that counts for this

Anyway, I make sure to rm -f all autotools-generated files in the autogen.sh
script BEFORE I regen the autotools stuff (except for the docs, such as
COPYING, etc). This keeps stuff like install-sh always up-to-date ;-)
*AND* I make sure to get a properly up-to-date GNU config (config.sub and
config.guess) setup in at that time too, since THAT is a royal pain in the

> already set up a tool which automatically removes the files generated by
> the autotools
> (perhaps this tool exists and I don't know about).

Probably because you don't really need it most of the time, even if you keep
the autogenerated files outside of version control...

  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 1 16:40:51 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.