On Tue, Nov 14, 2017 at 08:16:21AM -0500, Bo Berglund wrote: > On Mon, 13 Nov 2017 18:54:51 -0500, Bo Berglund > <bo.bergl...@gmail.com> wrote: > > >But now I have to deal with 6 different CVSROOT directories too... > >Is cvs2svn using the CVSROOT directory during conversion or can they > >be removed from the source so as not confusing the operation? > >Or do I need to use the cvsnt cvs.exe during conversion and does that > >in such a case need these admin files in CVSROOT? > > I found a post on the net stating that CVSROOT directory *is* > necessary but that cvs2svn does not use any info therein during > conversion. > See: > http://tigris-scm.10930.n7.nabble.com/Is-CVSROOT-dir-mandatory-when-using-cvs2svn-td57397.html > > However, I believe that I need to use the flag --use-cvs in order to > parse the CVSNT repository properly and this might mean that cvs > itself will use CVSROOT for something. > And then I have the problem of stuffing projects from the 6 different > repositories into SVN: Which CVSROOT should be used during conversion? > Or can all of them be there at the same time?
In this case, an initial cvs2svn conversion which creates 6 distinct SVN repositories might be easier. Note that you could later on merge these repositories with SVN tooling: http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate > CVSNT specific stuff: > --------------------- > I realized that I have used one CVSNT specific item and this is the > keyword -kbx, which means that some binary files have been marked as > binary with the exclusive editing flag. Typically this involves > Microsoft Office documents and PDF:s, which we did not want any two > persons simultaneously editing since they could not be merged. The SVN feature corresponding to this is the svn:needs-lock property. See http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html > Can cvs2svn deal with the -kbx keyword, for example by treating it as > -kb? > Or will these files be in any way corrupted by the conversion? Subversion does not need any special options for binaries. Keywords in files have to be explicitly configured on a per-file basis: http://svnbook.red-bean.com/nightly/en/svn.advanced.props.special.keywords.html File content is never modified by default -- what goes in comes back out. So I expect this problem will turn out to be irrelevant.