Re: Feature request: svn clean

On 17 March 2005, Martin Aliger said:
> I'd like to stress this stuff - it would be _very_ usefull in automated
> builds environment (like ccnet.sf.net). Those environments could have alot
> of "build artifacts" that is unversioned files but have to begin with clean
> copy. Should we leave cleanup for makefiles? No - we are suppose to prepare
> clean environment for builders. Delete all+fresh chekout is _very_ costy
> operation and "svn revert -R;svn update" works only sometimes.

Sounds to me like you need to write the pipeline

  svn st | awk '/^\?/ {print $2}' | xargs rm -f

in Python and call it svnclean. Or write it in C if you really can't
assume anything about your build environment (except for a C compiler).
I don't see a burning need for this to be built-in to svn, and it could
be dangerous. ("Ooh, what's this new clean command do?" ... shortly
followed by the sound of a careless programmer getting burned.)

Or use a modern build tool like SCons: "scons -c" deletes all build
targets very nicely. No more forgetting to add foo.tmp.mumble to your
"clean" target -- if SCons builds it, SCons cleans it.

        Greg

-- 
Greg Ward <gward_at_python.net>                         http://www.gerg.ca/
If you and a friend are being chased by a lion, it is not necessary to
outrun the lion.  It is only necessary to outrun your friend.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org