🚀 go-pugleaf

In article <1992Oct8.075927.4437@ericsson.se>, etxabju@juno.ericsson.se (Anders Bjurman) writes:
|> I works with a medium sized programming project (about 150 source files)
|> and currently uses the RCS posted to c.b.os2 some months ago (5.6?) to keep
|> track of different versions.
|> 
|> Since the CVS program included with RCS seems to be better I've tried to
|> use it instead, 
You are right!

|>but I can't make it work. I can't find anything in
|> the doc on how to get started, i.e. put my files under CVS control
|> ( ~ "CVS init" ). Is there some guide or hints on how to do that? (do CVS
|> *works* in the first place?)
Yes, CVS works. I use CVS at home (OS/2) for my projects. At work, we
are developing software in a work group on SUNs and use CVS. The
avaible CVS 1.2 port, done by Kai-Uwe Rommel, is somewhat buggy. The bugs
don't result from the port, the CVS 1.2 sources have bugs. I've ported
CVS 1.3 (the bugs of 1.2 are fixed, additional important features) to OS/2, 
but there are still some funny problems. The beta release will become
available very soon.

Documentation: You should download the CVS source from a GNU-Server. A lot
of papers are included. The 1.3 port will include the papers. 

For now check the foillowing things:
Set up all varaibles for RCS. Set up all variables for 
CVS (CVSROOT and EDITOR are important). Create a CVSROOT directory. Create the 
administrative directories (look at the sample tree). Create a
directoriy for your project in the CVSROOT directory. Goto some temp. 
directory. Say 'cvs co <project>'. Goto dir. <project>. 
Copy some source files (no binaries) to this directory and say 
'cvs add <file1> <file2> ...'. The check in with 'cvs ci'. 
|> 
|> I am also looking for some practical experience about version control in CVS
|> or RCS? In my opinon it seems to be too much work to keep track of 150 files -
We manage some projects (lot of files, C++, about 10000 lof each project) 
with CVS on our SUNs at work. 

The original author of CVS manages a complete UNIX OS
with CVS, the CVS papers include detailed information.`

It would be hard to do this SCCS or RCS alone.

|> I want to version control the application, not individual files. Any hints
|> on how to do that?
CVS is the optimal tool for this (as far as I know).

Lutz
-- 
// Lutz Gr"uneberg
// Lehrgebiet Rechnernetze und Verteilte Systeme
// Universit"at Hannover
// Schlosswender Str. 5
// D-3000 Hannover 1, Germany
//
// Email: Grueneberg@rrzn.uni-hannover.dbp.de
//
//				... have a  n.i.c.e. day