[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sccs2rcs to perl

From: Greg A. Woods
Subject: Re: sccs2rcs to perl
Date: Fri, 8 Mar 2002 15:07:50 -0500 (EST)

[ On Friday, March 8, 2002 at 13:24:16 (-0500), Michael Sterrett -Mr. Bones.- 
wrote: ]
> Subject: Re: sccs2rcs to perl
> Well, at this moment, we have 1835 SCCS directories and an absolute ton
> of source.  SCCS isn't the fastest thing to use -- I believe RCS blows
> it out of the water in the most common case of getting the most recent
> version out of the repository -- especially on NFS mounted disk, this
> gets to be an issue.

You really had better research that a bit more.  You are apparently
suffering from belief in a widely disseminated myth (caused by an
incorrect answer remaining in the comp.unix.questions FAQ since 1992,
perhaps because my colleague Ted Timar, who maintained that FAQ, was not
a huge fan of SCCS).  SCCS is not necessarily slower than RCS -- and RCS
_is_ still slower than SCCS in many cases, esp. if you use one of the
more modern SCCS implementations, such as Larry McVoy's BitSCCS, or Ross
Ridge's MySC, or even the GNU CSSC.

   A common misconception is that SCCS baselines the initial version and
   keeps deltas to create newer versions.  Actually, SCCS interleaves
   all the versions; this is not as bad as the common misconception, but
   it _can_ make new development get progressively slower.
Note though that if you don't use the head of the trunk for development
then RCS can degrade rather nastily....

In other words you'd better benchmark before you decide on that
assumption alone.

BTW, what the heck are you doing with putting any kind of repository on
an NFS partition!?!?!?!? 

> Perhaps more importantly, our development is moving almost entirely to
> Linux and the free SCCS support on Linux is lacking (CSSC isn't recommended
> by the author).

The current maintainer of CSSC is overly careful.  I've been using it
happily for years, even on occasion interoperating with it and SunOS-4.

> We'd also like to completely change our development scheme and move to CVS
> with maintainers of various subsystems accepting patches from developers
> similar to the free software model, but in-house.

Well, there could be benefits there, I grant you that!

                                                                Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]