[Biojava-l] Problems (slight) with the Biojava code in CVS

[Triplett, Terry]

> You noticed :-)

Heh.  It kind of jumps out at you <g>.
 
> For now delete all the coppies except 
> biojava-live/src/org/acedb, which is the
> correct one. Sorry - it got duplicated when I was moving the 
> acedb code from
> org.biojava.acedb to org.acedb - embarased.

Do you mean just that copy of acedb, or just keep that directory for
everything?

> We are trying to fix this as you speak - CVS is playing silly 
> buggers. Anybody
> got any ideas?

If you want a clean start, get the source together the way you want it, blow
away the current repository, initialize a new one and import the source
again. 
If this is too brutal, import the clean source into another place in the
repository (eg. cvsroot/goodcopy/<yourstuff>) and define a module for it.
Then checkouts of the module will grab only the stuff in 'goodcopy'.
Since you're just getting started, I would think the first option is best.
One weakness of CVS is that there is no easy way to move or delete things
once they are in the repository (at least in my experience).  Every single
time I have had problems with CVS it has been due to an attempt to move or
rename something.

> Matthew
> 
> ps all feedback, positive or negative is apreciated
> 
> "Triplett, Terry" wrote:
> 
> > I've successfully checked out the code via anonymous cvs, as per the
> > instructions on the biojava site.  Starting from the top 
> level directory, it
> > looks like the same code is present more than in the source 
> tree due to
> > nesting, and it's causing some trouble with the build 
> script.  For example,
> > a 'find' for acedb (starting from the top directory created 
> by cvs) shows:
> >
> >         biojava-live/src/org/acedb
> >         biojava-live/src/org/acedb/biojava-live/src/org/acedb
> >         
> biojava-live/src/org/acedb/biojava-live/src/org/biojava/bio/acedb
> >         biojava-live/src/org/biojava/bio/acedb
> >
> > >From this it appears that the acedb tree is present in 4 
> different places.
> > The build script fails with a number of 'already defined' errors.
> > I haven't analyzed this in depth yet (just got the 
> sources), so I don't know
> > whether the duplicate code is identical or not.  What I'd 
> like to know is
> > which particular part of the checked out tree is the 
> actively developed
> > code, so I can delete the extra kruft.  Better yet, it 
> would be nice to
> > clean up the cvs repository and/or define a module so that 
> a checkout
> > results in a single, well formed source tree.  This isn't a 
> showstopper,
> > because I can figure out what I need, but this will 
> undoubtedly confuse
> > everybody that grabs a copy of the repository.
> >
> > Thanks,
> >
> > "Do not meddle in the affairs of wizards, for you are 
> crunchy and good with
> > ketchup"
> > -- Unknown
> >
> >  <<Triplett, Terry.vcf>>
>