[Bioperl-l] Bioperl partitioning (was Re: SVN and ...Re: Perltidy)

[George Hartzell]

Nathan S. Haigh writes:
 > [...]
 > If the switch over to svn takes place, will all the Bioperl-* projects
 > move over at the same time? If so, will they go into their own svn
 > repository or into the same one? Since with svn you can checkout any
 > subtree of the repository I'm not clear on the pro's and cons of either
 > of these options.

I'm planning to drop the projects from the top of the CVSROOT into a
single svn repository:

    bioperl-ext bioperl-pipeline biodata bioperl-gui
    bioperl-run bioperl-cookbook bioperl-live biosql-schema
    bioperl-corba-client bioperl-microarray html bioperl-corba-server
    bioperl-network task-manager bioperl-das-client bioperl-papers
    xml-html bioperl-db bioperl-pedigree

although that's open to feedback from the core members.

As a progress report, I've built a demo repos with -run, -ext, and
-live in it and asked a couple of folks to to take a peek at it.  When
I get a bit further along I'll figure out how to get something for the
public to test.

 > Am I right in thinking that there is a way for cvs to define a "project"
 > such that when you checkout that "project" it actually checks out
 > multiple projects behind the scene? I'm sure I've seen this somewhere,
 > possibly when the project is dependent on some 3rd party code that is
 > also in cvs. If this is possible, I'm sure it will also be possible with
 > svn. This could then allow something like the following to happen after
 > the split up of Bioperl. The following projects could be defined:
 > bioperl-core, bioperl-graphics etc. Issuing a checkout of a "project"
 > called "bioperl" would actually checkout the real projects call
 > bioperl-core, bioperl-graphics etc. I may just be dreaming, but it seems
 > that this ought to be possible, doesn't it?
 > [...]

I don't think that there's any functionality like that in svn.

g.