Re: [Tcllib-devel] Regarding SourceForge, the Tcllib CVS, and transitioning somewhere.

[Kevin K. <kk...@ny...>]

On 02/15/2011 01:01 PM, Donald G Porter wrote:
> ...that's not been the history of these packages, and since a big part
> of SCM is preserving history, that presses toward keeping things
> together.
>
> Also, those packages are not separately releaseable in their current
> state.  (All the control over `make install` for them is over in Tcl's
> Makefile, etc.; their tests, docs, and ChangeLogs are all mixed into
> Tcl's).
>
> So for now, I've decided not to do that level of breaking up, and just
> accept that if breaking apart does become feasible later, it will be a
> more difficult task to confront then.

And not even *much* more difficult.  It's easy to *extract* history.
What's insanely difficult is to *merge* history.  Which is what we face
in any CVS->DVCS conversion; CVS maintains all history on the individual
files, and we're trying to reconstruct coherent changesets and branch
histories from the histories of the files.  Once you have changesets,
it's easy to filter out only those changesets that affect a given
set of files and lift them out.  (Not trivial, but much easier than
a CVS conversion.)

-- 
73 de ke9tv/2, Kevin