Re: Looking for suggestions on repository design
Thanks for the suggestions. I will take a look at it here and see what I
come up with.
On 4/30/05, Mark Phippard <MarkP@softlanding.com> wrote:
> The easiest thing to do, IMO, is to treat this like you would if this was
> variant of your own app. Use branches.
> Create a trunk for the vendor code. Then copy the trunk to create a branch
> for your modifications. When you get new code from the vendor, just copy
> it into a checked out WC of trunk and commit. Then merge that commit into
> a WC of your branch.
> The hardest part is just taking the drop from the vendor and getting it
> committed. In your case it is a bit easier than normal since I believe
> Lawson is just sending you their changes. So you do not need to figure out
> what has changed. Also, given that it is RPG and they know that people
> modify it, they probably do not do any deletes or renames of existing
> source. If they do, you just need to replay those actions in your WC for
> their code.
> I do something like this to manage our port of Subversion to OS/400. In my
> case it is of course much easier since the development is all really
> happening in the same repository. Your only challenge is really in
> simulating the actions of your vendor in their code line. It should be
> pretty easy, though, for the reasons stated.
> Good luck.
Midrange Programmer/Lawson Software Administrator
Want Gmail? Email firstname.lastname@example.org to get on my waiting list.
Received on Mon May 2 15:57:18 2005
This is an archived mail posted to the Subversion Users