"S. Cowles" <scowles_at_ckhb.org> writes:
> 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
> homedir.
This is not meant as a criticism... I am interested in hearing more
about your approach... however what you wrote above comes over to me
as sort of gobbledeegook...
Like:
> to the configuration management construct of an explicit list that
> specifies each file that should be included. i have broadened the
> concept
What the heck does that mean?... I'm not really asking for an answer
to that... just a pointer to somewhere I could read in plain english
what this setup is..
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2407235
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-13 23:14:40 CEST