RE: SCCS to Subversion

> Tim Alsop" <Tim.Alsop@CyberSafe.Ltd.UK> asked:
> > Has anybody had the need to export an SCCS repository and
> import it into
> > an SVN repository? If so, how did you do it and what should I use or
> > watch out for?
>
> Sort of...

Jonathan Leffler has described his sccs2rcs and rcs2svn
toolchain better than I can, but let me add one thing:

I'm another one who has dragged around SCCS, and RCS,
and CVS, etc., files for many years.

As well as converting, I have also found it useful
to actually check the SCCS files into RCS/CVS, and
now SVN. I.e. the actual SCCS files that contain the
versions, not just the checked out files.

This way you still have the original history.
If you do this, it's a good idea to also have checked
in a version of the SCCS programs/tools, so that if you
check things out in 2050, you have a chance of being
able to run them.

I've also checked RCS ,v files into CVS. Did that mainly
of twiki... I don't know that I'd recommend the practice,
but it does work. Umm, merging is dangerous... Overall,
it's better to check in tar/zip that to check an actual
RCS file in.

---
I've never done it myself, but I know some guys who
create a filesystem that resembles the SCCS archive:
instead of bar/foo.c, delta 1.1, 1.2, 1.3, etc.
they create
    bar/foo.c.dir/1.1/foo.c
    bar/foo.c.dir/1.2/foo.c
    bar/foo.c.dir/1.3/foo.c
They then imported that into their next VC system.
Hmmm.... looks a little bit like Subversion's
approach to tagging and branching, doesn't it?
---
I have every expectation of someday having to check
a Subversion repository into whatever is the next
big VC system.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org