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

Re: Dropping Subversion

From: Marcin Kasperski <Marcin.Kasperski_at_softax.com.pl>
Date: 2004-04-03 00:30:33 CEST

Dnia pią 2. kwietnia 2004 23:52, John Peacock napisał:
> Marcin Kasperski wrote:
> > In SVN tags/<all-the-tags-on-repo> recommended convention
> > kills immediately, other conventions are imagineable but
> > either require heavily loaded tags directory which at least
> > RapidSVN opens looooooooooong, or kills the ability to
> > checkout the trunk version of the whole repository.
>
> Who said you had to have all of your tags in one basket? You
> need to read the book, specifically:
>
> http://svnbook.red-bean.com/svnbook/ch05s04.html#svn-ch-5-sect
>-6.1
>

I read the book. And I am even commenting on it.

The convention:
/
   calc/
      trunk/
      tags/
      branches/
   calendar/
      trunk/
      tags/
      branches/
   spreadsheet/
      trunk/
      tags/
      branches/
works only when the projects are totally independent (in fact, it
is close to using separate repositories) and even then it is
hard to use for someone who works on many projects. The main
problem with this structure is that one can not easily checkout
or update the trunk of the whole repository without accidental
checkout of all the tags and branches.

Same for the next one.

To protect a developer from accidental checkout of all the tags
and branches, subversion repo must be organized so tags
constitute separate tree. And then we get to the problem of
inefficient huge tags&branches bag which can not be easily
navigated to from the working copy.

> You can structure your repository any way you want. If your
> libraries are all very independent of each other, each can be
> a "top-level" project; if they are closely related, you can
> group them. You can do whatever you want.

It just seems to me there are no way I can structure it to be
happy. Even restricting myself to two simple requirements:

- I can issue single checkout command and get the trunk version
of all the modules contained within the repository (or its
selected part)

- working on some module, I can easily and efficiently find and
operate the information about the tags placed on this module,

And one more thing: consider the fact, that many programmers need
some kind of GUI. Whatever convention will be used by me, it is
unlikely RapidSVN, TortoiseSVN or other GUI will support it.
Instead of sth like 'right-click Log' I will have to do 'open
new window, locate the tags directory according to the
convention, view its contents'.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 3 00:30:53 2004

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.