Re: [Jython-dev] directory structure (re: workings)

[<bi...@de...>]

Alan Kennedy wrote:

> [Brian Zimmer]
>  > Losing history is really the biggest loss as far as I'm
>  > concerned.  In my own projects and at work I have often found
>  > that a  better laid out directory structure outweighs the
>  > usefulness of history.  If you have a tag at the time of
>  > the restructuring it's always possible to go back and see it.
>  >
>  > It's too bad CVS is awful at this.
> 
> Indeed, I think the jython source base is now suffering from the worst 
> problems of CVS, and I like the idea of a re-organization.

Looking at the source layout I'm inclined to agree; CVS can result in 
inertia when it comes to code organization.


> However, if there was to be a re-organization, I would *greatly* prefer 
> a migration to subversion, which is a superior versioning system. Among 
> other things, it can version directories, and can move files around 
> without losing history, etc, etc, etc.
> 
> http://subversion.tigris.org
> 
> There are tools for migrating CVS to subversion, but I'm not sure how 
> good they are at carrying over history, etc, and don't have the time to 
> research it. But the code re-organisation could then be done *after* a 
> move to subversion, thus preserving history on files as they move around 
> the hierarchy.

I've migrated a number of projects big and small to Subversion from CVS; 
  it is usually a straightforward task. I agree it's a better tool than 
CVS, especially so for Java. IDE support could be better, but there are 
decent standalone tools available now.

Switching vcs should not be done on a whim however - imo it's a much 
bigger deal than a CVS restructuring.

[cvs2svn.py needs to work on the ,v files directly. It the event that 
this is what people want to do, it can be tested on a sourceforge 
repository tarball.]


cheers
Bill