[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Advice on setting up my repository

From: Malcolm Smith <mjfreelancing_at_optusnet.com.au>
Date: 2007-04-02 14:44:17 CEST

Jon,

On items 2&3 - I have no control over the location of the compiler output as
the generated files are required by the IDE itself. They must be located as
originally indicated:

> 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

Let's take cbuilder5 for an example sake:

Each of the projects generate files of unique names and they must all go
into the same BPL folder. So let's say we have:

  Proj1.bpl
  Proj2.bpl
  Proj3.bpl

Each 'Proj' will have other files associated with it in the LIB folder

  Proj1.lib
  Proj1.bpi

  Proj2.lib
  Proj2.bpi

  Proj3.lib
  Proj3.bpi

(unfortunately all files must co-exist in the one single folder for the
given compiler)

What would be nice is if I could commit 'Proj2' and only have the files
associated with that project committed, rather than everything in that
folder.

I've been spoiled with this ability in another product.

Looks like I'm going to have to think very carefully about how I design
things the second time around.

Malcolm Smith
MJ Freelancing
http://www.mjfreelancing.com

Associate Editor
C++Builder Developers Journal
http://www.bcbjournal.com

-----Original Message-----
From: Jon Daley [mailto:tortoise@jon.limedaley.com]
Sent: Monday, 2 April 2007 22:31
To: users@tortoisesvn.tigris.org
Subject: Re: Advice on setting up my repository

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. [snip] - OK

> 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:
>
[snip]
>
> 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
---------------------------------------------------------------------
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:44:38 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.