On Fri, 09 Mar 2012 11:53:47 +0000, Les Mikesell wrote:
...
> > So the CI would rely on another piece of software, SVN in this case, to
> > know what it has created in terms of files. Well, it doesn't seem right
> > to me.
>
> So how would you propose doing this across different VCS? I don't see
> how adding a new command to subversion that would do the equivalent of
> deleting everything except svn metadata followed by a revert and maybe
> an update helps with VCS independence. Your CI already has to know
> how to use each VCS independently anyway.
Yes. But knowing to invoke 'svn update' and 'svn cleanup -fdX' is somewhat
different from knowing to "svn status --no-ignore | awk '/^I / {print $2}'
| xargs rm -rf" (or similar) with all the caveats that come with strange
characters in file names.
If you argue that a CI/XY tool should find out for itself what files are
not under svn control then one could argue analogously that it should
as well bypass svn for doing updates. :-)
But then, svn currently has more important issues than implementing
'svn cleanup'.
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
