Package README (CVS ver. 1.1.1.1)

Bare minimal wrapper around CVSFile and portal_versions from CMFStaging.

This is very ugly.  The biggest reason being that CVS is a nightmare
because its old and is lacking a proper API.  Couple that with how
Staging/PloneStaging work by default and you can get soeme cases where
things become very unhappy.

  - Case:

    Someone accidentally opens up a new version and saves it w/o changing
    anything.
    This will not increment version numbers in CVS - but will in Plone.  This
    will
    most likely throw off any effort to compute what version we would like to
    revert
    to in the future ;-(

On the bright side?  You could protect these edge cases from happening
inside of your app.

On the dark side?  I'm not going to do it unless I get paid.

How to make this work:

  - CVSFile + CVS client and check out of a CVS module has to be on the
  Zope system

  - CMFCVSFile needs to be installed as a portal_type

  - portal_files should be installed (CMFExternalFileTool)
  You will need to configure your basedir path in the portal_files
  pointing to the absolute path of the CVS module you have checked out.

  - you will need to install PloneStaging (or CMFStaging)

  - replace the portal_versions with this versions tool

Caveats

  - If you are running CMF 1.3.1 you will need to remove the string:$ business
  in the
  portal_types -> action tabs