T E Schmitz ha scritto:
> Hello,
> I'm sorry I couldn't think of a better subject line. I just can't get my
> head around this:
>
> I am just about to set up a project which I checked out of its
> Subversion repository: OFBiz (www.ofbiz.org).
> It's an ecommerce application (and more), which has to be adapted for
> each website which it's going to be used for. The config files,
> templates and code to be adapted are scattered throughout the huge
> directory tree.
>
> I would like to maintain the project under version control myself to
> keep track of the revisions of that particular ecommerce site I am
> setting up. On the other hand I would need to maintain the link to the
> OFBiz repository in order to get updates.
>
> As I say, I can't quite see how to set this up. Any recommendations
> welcome.
>
Have you read the section about vendor branches on the svn book ?
I think it might be helpful to you.
Meanwhile, what about a workflow like this (just a thought):
- checkout ofbiz in its own subtree
- whenever you want to start a new ofbiz-based site, 'svn copy' the
ofbiz subtree to a new one (e.g. /site1)
- the ofbitz subtree can be kept up-to-date with the product repository
via the usual svn update command
- since all the sites are a copy of the same codebase, whenever an
update is made to the ofbiz subtree the changes can be propagated to
them as if they were branches of the same project.
Marcello
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 21 09:12:33 2005