Autmated svn adds and commits

[Garrett McGrath <gm...@Princeton.EDU>]

I'm presently attempting to write a simple script for placing all the config
files for a number of servers into a working copy area of an svn archive.  I
would like to then automatically commit this data to the svn archive itself
to make sure we have all our config backed up in an easy to access location
(and can step thru them to find things we've changed / broken).  Copying the
files and commiting them via cron job scripts is fairly trivial but it
appears your supposed to use an svn add command and svn remove command to
update the working copy's information.
 
Is there anyway to tell the working copy to just commit everything it has in
it's directory area?  So if I add a file it's assumed to be new and of the
latest revision number and if a file is missing it's assumed to have been
removed?
 
Basically we know the files are going to be there unless we remove them from
the copy script and delete them from the working directory (you need root
access to get to this particular area) so we would like to setup svn (for
only this location) to just assume whatever is in the directory area is the
most up to date files and commit them.
 
 

Re: Autmated svn adds and commits

[Ryan Schmidt <su...@ryandesign.com>]

On Nov 7, 2006, at 08:37, Garrett McGrath wrote:

> I'm presently attempting to write a simple script for placing all  
> the config files for a number of servers into a working copy area  
> of an svn archive.  I would like to then automatically commit this  
> data to the svn archive itself to make sure we have all our config  
> backed up in an easy to access location (and can step thru them to  
> find things we've changed / broken).  Copying the files and  
> commiting them via cron job scripts is fairly trivial but it  
> appears your supposed to use an svn add command and svn remove  
> command to update the working copy's information.
>
> Is there anyway to tell the working copy to just commit everything  
> it has in it's directory area?  So if I add a file it's assumed to  
> be new and of the latest revision number and if a file is missing  
> it's assumed to have been removed?
>
> Basically we know the files are going to be there unless we remove  
> them from the copy script and delete them from the working  
> directory (you need root access to get to this particular area) so  
> we would like to setup svn (for only this location) to just assume  
> whatever is in the directory area is the most up to date files and  
> commit them.

I don't think so. You may be interested to read this:

http://subversion.tigris.org/faq.html#wc-change-detection



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org