Duncan Murdoch wrote:
> On Mon, 04 Apr 2005 21:15:24 +1000, Mike Dewhirst
> <miked@dewhirst.com.au> wrote :
>
>
...
>>I'm having trouble deciding on a repository layout because it is really
>>four apps not one.
>>
>>There is a core app in its own root directory which is where most of the
>>development takes place. The other three have their own root directories
>>with physical copies of the absolutely common code. All four have their
>>own unique modules on top of the common stuff.
>>
>>You could think of it as all four sharing the same accounts receivable
>>but with separate market specific front-ends.
>>
...
> I would think of this as 4 separate projects, and organize it like
> this:
>
> coreApp
> trunk
> branches
> nextAppbranch
> thirdAppbranch
> lastAppbranch
> tags
> nextApp
> trunk
> branches
> tags
> thirdApp
> trunk
> branches
> tags
> lastApp
> trunk
> branches
> tags
>
> Then when you check out nextApp, thirdApp or lastApp, you also check
> out the relevant branch of coreApp to work with it. This is what
> externals definitions (see Ch 7) are for.
Duncan - thanks. I'll read Ch 7 (again?) and see if it helps.
I had actually been thinking along the lines suggested by Andrew ...
Andrew Thompson wrote:
...
> trunk
> common
> appOne
> appTwo
> appThree
> appFour
...
> If you want to "freeze" your common code, tag it and update your
> externals to point to the tag. Then you can continue development and
> possibly modify your common code without breaking your releases.
Thank you both - I'm progressing.
Regards
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 4 15:45:13 2005