But wouldn't the svk approach require that the "vendor" (that "open
source application" that Andres mentioned) also use the svk wrappers as
well, to manage the official repository?
To my untrained ears, this problem sounds more like the "vendor branch"
pattern. That's a pattern I've never taken the time to understand,
though, so I may be completely off base.
One possibility I can think of is to get a pristine vendor copy. Then
apply your customizations manually once more. Next, generate a unified
diff, representing the difference between the "vendor" code and your
code. Save that diff file somewhere. Next time you get a new vendor
release, apply the unified diff once again. I've never done this, so
this approach may be incomplete or have unforeseen side effects, but it
might be a path worth pursuing if the "vendor branch" pattern (whatever
that is) doesn't work.
Steve Dwire
-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Friday, August 27, 2004 12:43 PM
To: Andres Paglayan
Cc: Svn users
Subject: Re: best recommended procedure?
On Fri, 2004-08-27 at 12:39, Andres Paglayan wrote:
> Hi all,
>
> I have this situation,
>
> We are using an open source application which is publishing its
> Subversion repository on the internet through http, and they are
> committing changes every day. I don't have commit privileges over that
> tree.
> Ti fit our needs, I have many files tweaked and many others added to
> that project.
> Every time I download the latest version I need some -a lot of- time
> manually re-plugging my changes to that project.
>
> I have a Subversion installed in a Linux box and I use xp,
>
> My question is,
> Which would be the best way to create a branch from that project,
> considering that I can only read that repository?
>
> Would check out that repo and store it locally work? svn will not see
> remote changes on their server,
> Will then checking out that project daily work? svn will not keep
> track of the paired main/branch since the main is happening in a
> different servers.
>
> Can Subversion create a branch in my local server that is bonded to
> the trunk in theirs?
> if so, can someone point me in the right direction,
> if not, I will appreciate to hear any recommendation.
Subversion is a centralized system -- only one repository.
You sound like a perfect candidate for a decentralized system, where
everyone has private repositories. Try svk (http://svk.elixus.org),
which is a such a system, built on top of Subversion. You might also
want to look at the "Arch" vc system.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 27 20:10:31 2004