I'm redesigning my repository because I got it wrong the first time.
I started to write this email to the SVN list but I need to ask in terms of
the TSVN Explorer interface, so I hope I'm asking on the correct list.
Imagine I have projects on my HDD, like so
1. Since the last 3 items depend on code from MJFAF\ I get the impression it
is probably wiser to create one repository, say 'projects'. I can then
configure access to users such that they can only access the specific
folders applicable to them. Is this a fair assumption ?
2. Each of the 4 projects place their output on a completely different drive
when compiled - this is where I'm stuck in managing the repository.
In fact, each project can be output to 6 different locations (I compile the
code using 3 different compilers). These locations are as such:
c:\<path to cbuilder5>\projects\bpl
c:\<path to cbuilder5>\projects\lib
c:\<path to cbuilder6>\projects\bpl
c:\<path to cbuilder6>\projects\lib
c:\<path to bds2006>\projects\bpl
c:\<path to bds2006>\projects\lib
Does this mean I need to create 3 more repositories: 'cbuilder5',
'cbuilder6' and 'bds2006' and place the \projects\bpl and \projects\lib
folder under each of them ? If I'm not mistaken, I cannot place these
folders in the 'projects' repository because the locations are on completely
If so, how do I ensure the bpl\lib folders are committed when I commit any
of the project source code ? For example, if I commit the MJFAF project
source, how do I ensure the 6 paths just mentioned also get committed.
Similarly, if I 'update' a project will all folders (on both drives) get
<I'm thinking 'externals', but am not sure>
3. My biggest question comes from item (2). I need to ensure that 'updates'
for a particular project not only update the source and bpl\lib folders BUT
I also need to make sure that the ONLY bpl\lib files that get updated are
associated with the selected project - I don't want the bpl\lib files from
the other projects also updated.
I hope this all makes sense. Any and all help/comments welcome.
C++Builder Developers Journal
Received on Mon Apr 2 06:07:20 2007