Commit Graph

9 Commits

Author SHA1 Message Date
todd
a40e980fb1 opencm-alpha18pl2 .. another upwards-only compatible update 2002-10-23 20:57:30 +00:00
todd
e2e50ffba9 update to alpha18pl1
WARNING:  Anyone using OpenCM must realize that with this update, you will
          no longer be able to talk to older repositories.  The repository
          itself upgrades fine, just the wire protocol changed incompatibly.

Recap: alpha18pl1 and beyond will not talk to alpha17 and below, and
       vica versa.
2002-10-23 15:35:54 +00:00
todd
6e9c7cab13 update to alpha17 (finally some activity!) 2002-10-11 12:27:00 +00:00
todd
106390e2e4 respect CPPFLAGS 2002-09-12 15:26:33 +00:00
todd
6b35f41b29 we use ${LOCALBASE} here, not /usr/local 2002-09-12 15:08:57 +00:00
todd
2076b86927 use gc.h and co from /usr/local/include 2002-09-12 15:07:23 +00:00
todd
0aa50eff78 64bit stuff breaks in bad ways. more testing needed 2002-08-28 22:23:29 +00:00
todd
42c5ea0ac6 from wilfried@ .. properly use LIB_DEPENDS and use the PLIST${SUBPACKAGE} so
we don't end up with two packages with docs with the docs flavor. Thanks!
2002-08-28 14:38:25 +00:00
todd
47060f5673 OpenCM alpha16
OpenCM is designed as a secure, high-integrity replacement for CVS. A list of
the key features can be found on the features page. While not as ``feature
rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM
provides first-class support for renames and configuration, cryptographic
authentication and access control, and first-class branches. 

The OpenCM project was originally started because we needed a secure,
high-integrity configuration management system for the EROS project.
Alternatives, such as BitKeeper, Subversion, and PerForce, either did not
meet our requirements or were not available at the time the work started. We
had previously used CVS, but it's absence of real branches and configurations
finally drove us to build a better tool.
2002-08-27 16:46:09 +00:00