Hello,
I checked the FAQ and this list's archive but could not find an answer. I have the following at hand in a Windows2003
server/WindowsXP environment. Only in case use of subversion would deliver a workable environment, I like to convert the
directory/file structure described below to a subversion repository.
1. The current "repository" consists of a number of top level directories, each containing a variable number of nested
subdirectories with a variable depth.
2. Each subdirectory level in this structure represents a different software version to be maintained.
3. Each directory level only contains those files in which it differs from its parent directory level (note the
recursive nature of this!). For building purposes these files have precedence over the files with the same name/type in
higher levelled directories.
4. There is a kind of common pool of files.
5. A "working copy" with all files needed to build a version can be created by copying all files in the directory tree
upward, starting at the version's own level and finally that common pool, thereby keeping remark 3. in mind.
In a simple picture it looks like this:
\Common
\H
\C
\...
\MainTree1
\Sub11
\Sub111
Some files
\Sub112
Some (maybe) other files
...
\Sub12
\Sub121
Files
\Sub122
Other files
...
...
\MainTree2
...
Maintenance of this directory/file structure has always been taken care of by me, being the only one with 'write' rights.
I studied the following document entirely:
svn-book.pdf
Version Control with Subversion
For Subversion 1.3
(book compiled from Revision 2354)
in an attempt to find clues for an answer to my conversion needs. However, I am afraid that by subversion design,
benefits (yes there are!) from the current set-up (like the visible relationships between versions in the directory/file
structure, files with same date/time and contents for comparison purposes, which version has the same features and so
on) will be lost when I simply import all files needed for each version (what I called my "working copy" above) into a
subversion respository.
Is there anyone that has experience converting such a software maintenance set-up into a subversion repository without
loosing (too much) implicit and explicit relational information?
Best regards,
Henk Wissink
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 8 16:36:14 2006