Marc Sherman <firstname.lastname@example.org> wrote on 08/16/2005 04:19:12 PM:
> David Weintraub wrote:
> > I have personally found that distributed systems aren't all that
> > distributed. Most developers don't want other users using their
> > machines for syncing back and forth to the archive. Instead,
> > developers depend upon a very few machines that become the central
> > archive for everyone. In the end, everyone is syncing to the same
> > servers and hitting the same bottle necks.
> Distributed systems also support hierarchical layered development, which
> SVN currently doesn't directly support very easily.
> For example, at my company, we maintain a private local fork of
> Subclipse which we use internally. Currently, we do that using a vendor
> branch, which is updated each time Subclipse releases. It would be nice
> to be able to do that by having our local repo synch from the Subclipse
> repo, but one-way only, so that our local mods never get synched
> upstream (where they're not wanted). That way, we could build our mods
> based on any arbitrary trunk rev of Subclipse, just by forcing a synch.
I do this using Subversion and svk.
I have an internal Subversion repository running on a server on my network
(in my case an AS400/iSeries). I run svk to maintain a mirror of the
Subclipse and TortoiseSVN repositories on my iSeries. In the same
repository, I then use Subversion to maintain a branch of Subclipse and
TortoiseSVN for my private fork. Developers work against these branches
using normal Subversion techniques, and can merge the latest from
Subclipse or TortoiseSVN whenever they feel like it.
So I am only using svk to maintain a mirror of the repository, I am not
using it for any of its other features.
This solution has worked well for me.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Aug 16 22:28:51 2005