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

Re: Expresso vendor branching

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-14 14:04:39 CEST

On Wed, 2004-07-14 at 06:22, Mark Kikken wrote:
> Hi,
> I'm using the Expresso framework and plan to use Subversion in the
> future to manage any Expresso-related development. I've read the
> subversion manual and came across the 'vendor branching' section. It
> made sense, and I want to do the same for expresso.
> However, the problem with expresso is, that it is not exactly a branch.
> Expresso is a fully-functional web-application in itself, and not just
> some files in a subdirectory of my project. The idea is that you add
> classes to the expresso source to add functionality and register these
> as an application with expresso. So, it's more like writing a vendor
> branch for Expresso, than the other way around.
> To make things even more complicated, the expresso sourcecode-tree has
> the be restructured to be able to use it with the Eclipse IDE (which I
> intend to do).

Your descriptions sounds something like the way one writes a Zope
application. You create classes and subclasses within Zope's own code
framework, and then 'register' your code as a 'product' within Zope.
But a Zope product still lives in a subdirectory, so I've had no problem
keeping my Zope product under version control; my Zope product
directory also happens to be subversion working copy.

So if Expresso is like this, then you could do the same thing. There's
no need to compare anything to 'vendor branching'. I don't think that
term applies here at all.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 14 14:07:18 2004

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.