History for TrackerCVSInstructions

??changed:
-
    The Tracker runs as a Zope Product including some ZClasses,
    External Methods, and a python product.  The whole kit is
    available via read-only public CVS from cvs.zope.org.

    You can either get a CVS checkout (see below), or download a tarball
    directly from the CVS web interface. A CVS checkout allows you to get a
    updates from CVS at a later date, but the web interface doesn't require you
    to have cvs installed. The tarbal lis available from a link at the bottom
    of the "CVS web interface for 
    Products/!TrackerBase":http://cvs.zope.org/Products/TrackerBase.

    The read-only access is based on the CVS *pserver* mode.  To use it
    you will need to be running version 1.9 or better of CVS.  For leads
    on CVS distributions for all prevalent platforms, and executables
    for Win 32 systems, see "Cyclic's web pages":http://www.cyclic.com/.

    (These instructions are very similar to the instructions for the
    general Zope CVS checkout; you can find a link to *those*
    instructions at http://www.zope.org/Resources/CVS)

    If you haven't used the Zope public CVS repository before you'll
    have to login first - you only need to do this once for your
    account, from then on the credentials will be obtained from a file 
    where they're stashed by this login process.  Here's the command::

      % cvs -d :pserver:[email protected]:/cvs-repository login

    (The **-d** option identifies the repository, indicating *pserver*
    mode, user *anonymous*, host *cvs.zope.org*, and directory
    */cvs-repository*.)

    You should be prompted for a password, which is *anonymous*.

    You only need to log in once - it causes (on unix - not sure about
    windows) a file named .cvspass to be created in your home
    directory, with a (crudely) encoded version of the password
    associated with the server.  Subsequently the password will be
    sought from this file, so you don't need to worry about it unless
    the file gets clobbered.

    Once your login is established, you can do your initial check
    out.  Change directories the lib/python/Products directory in the
    site where you want to install the tracker and do::

      % cvs -z7 -d :pserver:[email protected]:/cvs-repository \
            checkout -d !TrackerBase Products/DC/!TrackerBase

It appears that there has been a CVS module reorganization.  The module can now be found as Products/!TrackerBase, making the cvs command:

% cvs -z7 -d :pserver:[email protected]:/cvs-repository \
           checkout -d !TrackerBase Products/!TrackerBase


    (**-z7** says to use a substantial level of compression, balancing
    CPU and network bandwidth.  The '\' backslash makes the second line a
    continuation of the first - you could put it all on a single line,
    without the backslash.)

    This should issue several check out messages, creating a
    directory named !TrackerBase, with the distribution inside it.  This
    initial checkout creates a copy of the source files together with
    some CVS bookkeeping (in directories all named CVS) which keeps
    track of the repository and login information.  You shouldn't need
    to repeat the checkout *except* for certain occasions when a new
    module has been added to the repository.  In such cases, redoing
    the checkout will add in the new content without distubing what's
    already been obtained.

    The file README.txt contains Instructions for the other things you
    need to do to install the tracker (including importing the Tracker 
    ZClass, and so forth).

    Once you've done these initial steps, you can stay current by typing::

      % cvs -z7 -q up -P -d

    (**-q** says not to spew about unchanged files, **-P** says to prune
    empty (eg, obsolete) directories, and **-d** says to check out newly
    added directories.)