[Novalug] Linux SCCS alternative

Derek LaHousse dlahouss@mtu.edu
Thu Nov 21 09:28:20 EST 2013


Um, my local tree is my master.  That's where I would want a commit to
go.  If someone wants to accept my changes, they can pull from my
master and put it in their master.  That's correct.  UNLIKE EVERY
REVISION CONTROL SYSTEM THAT CAME BEFORE IT.


On Thu, Nov 21, 2013 at 9:24 AM, Andrew Beals <andrew.beals@gmail.com> wrote:
> For anyone who has used a revision control system before, I strongly
> disrecommend using git unless you have to.  The simple reason is that a git
> commit operation DOES NOT PERFORM AN ACTUAL COMMIT OF THE CODE UNLIKE EVERY
> REVISION CONTROL SYSTEM THAT CAME BEFORE IT.
>
> "But it commits to your local tree!"
>
> Which is not what any prior system did - prior systems would merge your
> changes with the master.  This is what people expect to happen.
>
> "But git has a command to do that."
>
> Git doesn't match "the pattern" of previous systems.  Git is "an
> anti-pattern".  (The entire "pattern"/"anti-pattern" concept has been beaten
> to death, but let's tackle that at another time.)
>
> "But I like git."
>
> That's nice.  I like pickled okra, but I don't run around suggesting that
> people have that on their sandwiches when they ask for pickles.
>
> "You're an old fossil and know nothing about computing."
>
> I built the technologies that allowed you to get on the Internet in the
> first place.  I invented the technology that will let you get decent
> wireless bandwidth in very crowded environments.  Here, have a cookie.
>
>
>
>
>
>
>
>
> On Wed, Nov 20, 2013 at 10:03 PM, James Ewing Cottrell III
> <JECottrell3@comcast.net> wrote:
>>
>> Peter, I am surprised at you! CVS is derived from RCS, which was written
>> as a Free Replacement for SCCS.
>>
>> To use an analogy, SCCS and RCS work at the File Level, much like cp.
>> CVS works at the Directory Tree, much like tar.
>>
>> CVS is Obsolete as a VCS. Use Subversion (svn) instead.
>>
>> Or better yet, use a Distributed VCS, like git, mercurial (hg), or
>> Bazaar (bzr). There are others, but unless you have a good reason, use
>> one of the last four I just mentioned.
>>
>> JIM
>>
>> P.S. Once again, DO NOT use CVS for new projects.
>>
>> On 8/10/2013 8:40 PM, Peter Larsen wrote:
>> > On 08/10/2013 06:15 PM, Jon LaBadie wrote:
>> >> As an old-timer UNIX user I've used SCCS for a long
>> >> time.  Not so much for software projects, but for
>> >> version control of course materials and for individual
>> >> configuration files.
>> >
>> > WOAH - that's an old timer .... SCCS became CVS, which got replaced but
>> > SVN which has now been replaced by git - and then there's the ton of
>> > diviations, commercial alternatives etc. and well, time for memory lane
>> > :)
>> >
>> >> SCCS was really convienent for managing individual
>> >> config files.  Do an 'sccs create <file>' and it
>> >> saves the current file in a ".SCCS" that it creates
>> >> if needed.  Do a 'get' to get an editable copy and
>> >> after modifying it, a 'delta' with comments describing
>> >> the change.  It is a lot nicer than having a directory
>> >> littered with Xorg.bkup, Xorg.orig, Xorg.bk, Xorg.old,
>> >> etc.  :(
>> >
>> > It still is - the concept of SCCS is exactly what CVS, SVN and GIT
>> > provide too. It manages versions of files - that even includes binary
>> > files, but it's really most useful with text files.
>> >> I'm looking for a Linux alternative for this type of
>> >> version control.  Can you suggest any candidates for
>> >> this type of single file version control?
>> >
>> > Well, all of the above can do it too. It's possible to keep the change
>> > repository local or putting it in a central place, which I would
>> > recommend.  However, doing it locally is just as easy.
>> >
>> > Here's how you'll use git ....
>> >
>> > To initialize git - this is a one time operation, you run "git init" in
>> > the directory where you have your files. Ie. in /etc or your
>> > $HOME/Documents folder.  Git isn't an editor. It just knows about how to
>> > track changes. So you'll usually edit/change your files as usual, and
>> > when you have a file you want to start tracking you use "git add" to add
>> > the file, and then when you've come to a check-point you simply do "git
>> > commit" on the file(s).
>> >
>> > If you want this to happen automatically you could add plugins like
>> > "fugitive" to vim or other editors, and there'll be no need for commands
>> > on the command line. SCM is build into IDEs like Eclipse making coding
>> > and source control integration very very easy.
>> >
>> > Once you have your files into git, you can do all kinds of cool stuff
>> > like "diff' or reversing files to old versions/checkins. The command
>> > "git status" gives you a great view of which files you have under source
>> > control, and which ones you may have forgotten, the status of the
>> > checkins etc.  It's pretty cool stuff.
>> >
>> >> I know of gnu's CSSC mimic of SCCS but I found no
>> >> packages for Fedora or CentOS.  I tried to compile
>> >> two different release versions but ran into errors
>> >> and did not try hard to figure them out.  The
>> >> project does not appear to be active, last update
>> >> was in 2010.
>> >
>> > SCCS is ancient. It was initially written in 1971 according to
>> > wikipedia. CVS, SVN and Git are all still part of fedora - where as with
>> > git you will still need to grab EPEL to get git.
>> >
>> >
>> >>
>> >> Jon
>> >
>> >
>>
>> _______________________________________________
>> Novalug mailing list
>> Novalug@calypso.tux.org
>> http://calypso.tux.org/mailman/listinfo/novalug
>
>
>
> _______________________________________________
> Novalug mailing list
> Novalug@calypso.tux.org
> http://calypso.tux.org/mailman/listinfo/novalug
>



More information about the Novalug mailing list