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

Re: Yet another repository layout question

From: Andrew Thompson <subversionuser_at_aktzero.com>
Date: 2005-04-04 15:16:01 CEST

Mike Dewhirst wrote:
> I'm just starting a legacy app rewrite in python on Windows. And I'm
> just starting to use subversion/tortoise hosted on my linux box's
> Apache. I haven't previously used subversion or similar.
> 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.
> In the past I have moved them forward in sequence. The core app gets out
> of beta first and when stable I copy the common code to another app root
> then get that working and so on.
> I'd like to keep the common stuff separately but I have to maintain
> older versions of it in the other apps at least until I roll all the
> users forward one app at a time.
> What might be a useful repository layout? I think I'm stumped.
> trunk
> coreApp (lots of common stuff plus unique bits)
> nextApp (ditto)
> thirdApp (ditto)
> lastApp (ditto)
> branches
> ?
> tags
> ?


svn co svn://server/codebase/trunk/appOne
svn propset svn:externals "common svn://server/codebase/trunk/common" .
svn ci -m "set external for common code folder"
svn update

This gives you a distinct folder for each app, with common code in one

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.

Andrew Thompson
Interested in a hosted SVN repository? Email me, let's talk...
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:18:35 2005

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

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