Re: about imports and cvs update

[Spiro Trikaliotis]

Hello Harry,

* On Sun, Mar 14, 2010 at 09:38:12AM -0500 Harry Putnam wrote:
> Michael Haggerty <address@hidden> writes:

> > To add a new directory hierarchy within a CVS repository, simply check
> > out a working copy, copy the new directories to the right place in the
> > directory hierarchy, then use "cvs add" and "cvs commit" to put them
> > under version control.
> 
> Well, that is true, but that method requires a lot more hand work if
> the added sub hierarchy is more than 1 directory and a few files.

It can be automated with two calls to find(1).

 
> Once an import has been done, as in this case.. is there any
> continuing harm?

Note that Michael is working on cvs2svn, a conversion tool to convert
from CVS to Subversion (SVN). I am sure he knows what he is speaking
about. ;)

I converted some CVS repositories to SVN with cvs2svn myself. Every
time, a vendor branch generated some problems which had to be solved by
hand, especially if the vendor branch was used in a way it was not meant
to be used. But, please don't ask me of the details, I don't remember.

 
> Sounds like you think cvs is on its last legs... I had hoped to
> continue using it for a good while yet.  Is it likely to fall out of
> development?

I don't think so. There are some alternatives, yes, but every one has
its pros and cons. What I like most is the ability of CVS to have a kind
of "view", that is, a checked out sandbox which combines parts of
different branches. With tagging in the right way, this can be totally
automated. Neither SVN nor git (the two you mentioned) have this ability
- at least, they did not the time I checked them.

Thus, I think every tool has its advantages and disadvantages. Use the
one which suits your needs best.

Best regards,
Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/