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

Re: Why rewrite the Subversion working copy?

From: Andreas Schweigstill <andreas_at_schweigstill.de>
Date: Thu, 24 Apr 2008 11:37:36 +0200


David Glasser schrieb:
> For the higher layer, I've been thinking about the design of
> "libsvn_workspace" and an "svn workspace" command, which allows users
> to define non-trivial working copy layouts, mapping one or more
> repository subtrees into their workspace. "switched directories" and
> "externals" wouldn't be special cases any more: they're just be normal
> things that show up in workspaces that aren't just a single repository
> subtree. Projects can be configured ad hoc using "svn workspace"
> commands, or in a version-controlled file (or property?), similar to
> svn:externals or the SVK svk:project:* property. Perhaps I (we?) can
> add this layer to the prototype I'm starting, before backporting it to
> C for the real svn_ws.

This is a really good idea. Some VCS like ClearCase implement the view
concept, which seems to be quite similar.

In a proper implementation there should be the possibility to store the
workspace and/or project setting in the repository, so a user which
doesn't have his private definition can choose wether he wants to get
the "bare" working copy or a working copy based on a default workspace
or project template:

svn co --workspace svn://server/workspaces/my_workspace \

svn switch --workspace svn://server/workspaces/my__other_workspace .

Andreas Schweigstill

Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-24 11:37:11 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.