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

Re: early reflections on subversion methodology

From: Saulius Grazulis <grazulis_at_akl.lt>
Date: 2005-07-29 07:44:44 CEST

On Friday 29 July 2005 03:42, Steve Williams wrote:

> > ... b) if the tools could hide these directories
> > (at least on the client side) and instead show them as 'views' - i.e.
> > the user would be in the mainline view, the branch-xyz view, the
> > release-0.8 view and so on. I don't think it would be hard to do.
>...
> As for clients hiding those directories, you would have to customize one
> of the many available clients (they are open-source after all) since
> what you are trying to hide is your own idea of a "real development"
> directory structure.

Actually, you can hide the directory of your project structure for developers
without any modification of the client:

Instead of checking out the whole repository:

svn co svn://server.domain.org/repositories/project1 whole-project1

You can just check out a trunk:

svn co svn://server.domain.org/repositories/project1/trunk project1

Or some branch:

svn co svn://server.domain.org/repositories/project1/RELEASE/version-11R6
project1-view-11R6

At your liking... :)

You can also switch your working copy between any of the branches, tags or
trunk.

Enforcement of the directory structure is a matter of project administration.
It is a very nice feature of Subversion that it does *not* impose any
directory structure on you. This was one of the reasons I chose Subversion...
Well, except for the need to have trunk/||tags/||branches/||, which is a very
mild requirement ;).

-- 
Saulius Gražulis
Visuomeninė organizacija "Atviras Kodas Lietuvai"
P.Vileišio g. 18
LT-10306 Vilnius
Lietuva (Lithuania)
tel/fax:      (+370-5)-210 40 05
mobilus:      (+370-684)-49802, (+370-614)-36366

  • application/pgp-signature attachment: stored
Received on Fri Jul 29 07:53:38 2005

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.