On Sun, 11 Oct 2009, Carsten Koch wrote:
> From: Carsten Koch <CarstenKochICEM_at_web.de>
> To: users_at_subversion.tigris.org
> Subject: Can my entire home directory become a subversion working copy?
> I am wondering if it would be possible to make my entire home directory
> a subversion working copy.
> Instead of doing backups, I would run
> svn commit ~ -m "`date`"
> every night. This would allow me to access every version of every file
> I ever had anywhere under my home directory.
> One way of solving all this might be to maintain a working copy
> separately from my home directory and writing python code that
> mirrors most things from the home directory to the working copy,
> automatically creates "svn add" and "svn delete" commands, etc.
> Is there an easier way to do all this?
> Has somebody perhaps already implemented it?
> Any thoughts and pointers are welcome!
one alternative that i have used for a few years, now, approaches this
problem in a slightly different manner.
my objective is to keep an entire, defined, development environment under
svn control. this is not an all-encompassing backup. the files kept under
svn control are specified in a complete list, where "complete list" refers
to the configuration management construct of an explicit list that
specifies each file that should be included. i have broadened the concept
so that the complete list in this case includes regular expressions and
sub-directories. updating the complete list is easy and the process is
data-driven so its changes propogate automagically through the chain of
subprocesses (commits, updates, etc). the process also requires that the
svn working copy be separate from the production environment (normal
working home directory). thus, working copy is just a subdir of the
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-12 20:37:55 CEST