Until today, I did not realize how badly.
The entire tests/ subdir is missing from the release, but is available if
you wish to checkout their repository. hmm...
- '=' vs '+=' can cause grief wrt depends
- BUILD_DEPENDS is not needed if it only contains LIB_DEPENDS
from nikolay@
- teTeX is no longer v1.x*, depend accordingly
Thanks guys!
see http://www.opencm.org/news.html for hilights of this update, major
noteworthy changes include:
- sxd has gone away, gzfs is 'interim' while 'sxd2' is almost ready
- if you have an old sxd repository, read the mailing list archives for
how to update (use an interum version)
- an incompatible update to the server/client protocol requires that you
update both at the same time
(as a reminder, this is 'alpha' and as such is subject to incompatible changes
like the above. expect more to come when sxd2 emerges)
Also, add a 'nogc' flavor that removes the dependency on boehm-gc, at the
cost of not free()'ing all memory allocated (read: at the moment, most).
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.
o rename three patches to 'update-patches' naming conventions
o add 64bit patches
o add other tidbits from my
opencm://opencm.org/everyone/todd@fries.net/home/merge-candidate
branch
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.
