On Mon, 2 Apr 2007, Malcolm Smith wrote:
> I'm redesigning my repository because I got it wrong the first time.
Yup, we all do...
> 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 ?
Sounds good to me.
> 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
> different drives.
>
> 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
> updated ?
>
> <I'm thinking 'externals', but am not sure>
Right, externals is what you want. You still have to run
update/commit in each of the directories, but the files will be able to be
stored in one shared place. I'd try to avoid making too many projects,
unless you have to. Do your three compilers output any of the same file
names that you need to have checked in? If so, you will have to create
multiple "bpl" directories, rather than just one shared with all projects.
If they all output different filenames, than you can simply have one bpl
directory in the repository, and then use svn:externals to share them, or
even better, you might be able to not use svn:externals, but check out the
bpl project three times, once in each location.
> 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 am not sure what this means. If you want to update the files
separately, it will be easiest to keep them in different directories,
otherwise you would have to update only particular files, and I always
find that hard to manage.
--
Jon Daley
http://jon.limedaley.com/
There's so much comedy on television.
Does that cause comedy in the streets?
-- Dick Cavett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Apr 2 14:31:01 2007