🚀 go-pugleaf

Tony Houghton <nospam@caspian.uklinux.net.invalid> wrote:
: In <8bo9ct$juv$1@wagner.wagner.home>,
: Victor Wagner <vitus@wagner.rinet.ru> wrote:

:> You are wrong. My former boss used to say "Each project have some files
:> and some developers. Project of one file and one developer can be
:> managed with just RCS. But if there is more than one of either files or
:> developers, you should use CVS." It seems that you have more than one
:> file.

: What are the disadvantages of RCS for more than one file?

That all the files managed separately.

You cannot just stop and say "It is release", With CVS you can
simply add tag say r_0_0_1 to mark current state of all files as
release. Then you can easily checkout (or export) all you files at the
moment of release no matter how much changes you have done since
release.

Other thing is making branches. If you are experimenting with changes
which affect more than one file, in CVS you do the branch and it is
maintained - you can easily switch between this branch and main one with
one command.  With RCS you have to branch each file separately.

And, how would you ship a project consisting of multiple nested
directories? With RCS you probably would need to write some script which
archives current sources omitting RCS directories. CVS already have
command cvs export for this.

-- 
You will not censor me through bug terrorism.
	-- James Troup