> You have CVS repositories for KAPPA, CONVERT, HDSTRACE and PAR, plus
I can confirm that it's just these four.
> David has taken over KAPPA, and Alan took over the other three.
Yes.
> done any other development on those packages since the handover.
I submitted my changes to David and Alan for incorporation. These were
mostly in CONVERT in early 1998.
> Thus the issue is one of preserving older history, rather than of
> merging any fork. Yes?
Correct.
> Of those, only PAR is in the repository at present, and I imported
> what was in the distribution tarball in /star/sources/par (with a
> couple of edits).
Probably little has changed in PAR.
> 3. Apply that patch to the head of the new repository, bringing it to
> the point that Alan left it, and commit that with a general `Alan
> dun this' comment.
Is there some quick fix using diff output to do this?
> If you wanted to preserve each of the releases in the repository, then
> you could do steps 2 and 3 in smaller steps, preparing a diff between
> separate Alan-releases, patching the repository, and committing and
> tagging that. That would be a bit of a slog (and doubtless scriptable,
> though I'm not aware of anything pre-written), and so I'd leave the
> decision about whether it's worth it to whoever'd have to do it.
I think HDSTRACE and PAR will be fairly easy to do. The biggest job
will be finding and mounting the CDs. CONVERT there was more done,
particularly for AST, but not a huge amount.
> Then the same for KAPPA, with Alan->David. Probably the same for PAR
> as well -- I can just junk or move aside the version of PAR in the
> current repository.
Probably easiest to compare the current versions to judge the scale of
what's involved before deciding whether its worth it or not. I feel
exposed not having code revision system for regular management having
relied upon CMS and CVS for many years. Since regaining CONVERT, I've
made and embarrassingly lost changes because of not having a modern CVS
repository to commit those bug fixes. It too easy to lose stuff with
tar archives not being updated.
> David? By `chosen directory structures' are you suggesting differences
> in the internal structuring of the KAPPA sources, in which case that's
> for you and David to fight out....
Yes. I've already sent David a directory listing of my KAPPA CVS tree.
> `Importing' CVS repositories is simple -- one just copies the CVS
> repository from its source into the correct place under
> cvs.starlink.ac.uk:/cvs.
We'll see.
> Have I got the right end of the stick?
Yes thank you.
Malcolm
|