Re: Configuration Management for Ada on Unix

[pautet@email.enst.fr (Laurent Pautet)]

In article <31A79E0A.2F99@hiwaay.net>, Bob Crispen  <crispen@hiwaay.net> wrote:
>
>It really just depends on what you need.  If you've got a number of
>simultaneous versions and targets and are doing a real product-line set
>of builds, you'll obviously need one of the professional products, while
>homebrew version control will do you if you have a handful of targets
>and have only a rolling 3-version system (Test, Current, and Delivery).
>
>Note that SCCS allows you to have several directory trees.  You can have
>one tree for each version, and within that trees for platforms (e.g.,
>common, vme, workstation).  SCCS can then load everything down to one
>big directory for each build.  Unlike the flat(ter) VMS filesystem, Unix's
>filesystem can be used as a serious helper for your configuration management
>tool.

Maybe I am wrong, but I think SCCS is very unefficient because it
stores patches between Version (N+1) - Version (N) and when you want
to access to version N, internally SCCS retrieves version 0 and
applies all the patches to obtain version N. RCS stores the last
version (rather than the first one) and differences between Version
(N) - Version (N+1).

Anyway, you should have a look at CVS. It provides a lot of nice
features, especially those you mentionned above. Basically, it's a
configuration and version system when RCS and SCCS are only version
systems.

-- 
-- Laurent