Installing PTK from CVS

Overview

This document describes the process of getting the PTK from the CVS repository, and installing it into your Zope. It assumes the following:

You want to install the "latest-and-greatest" version of the PTK from a CVS.
- See Installing PTK to install from a tarball.
- See the note below [1] if you want to export or check out the sources for a specific version from CVS.
You want to install the new, standard "filesystem-products-only" version of the CMF (no ZClass products). See Installing DemoPortal for directions on installing the (now deprecated) DemoPortal ZClass product.
You are installing the PTK "from scratch", with no previous versions of the software to replace, and no existing portals or content to migrate.
- See Upgrading PTK if you have previously installed an earlier verison of the PTK.
- See Andrew Sawyer's Migrating from CMF to PTK for notes on migrating and existing, DemoPortal-based portal to the new model.
- See Migrating Content from 0.7.1 if you need to migrate a portal and content from PTK v. 0.7.1.

Please note that current versions of the PTK (0.8 and later) require Zope 2.2 or later

For help with CVS in general, see the CVS Online Manual
For direcitons on using the Zope CVS server, see Public CVS Access; substitute ZopePTK for Zope2.

Quick Start

Those too impatient to Read the Fine Manual can download the quickstart script and run it; see the Quickstart Instructions for more details.

Installation

Fetch the ZopePTK package from the Zope CVS repository:

     $ cd /tmp
     $ cvs -d :pserver:[email protected]:/cvs-repository login
       <supply "anonymous" as the password>
     $ cvs -d :pserver:[email protected]:/cvs-repository checkout ZopePTK

     This checkou creats a directory, 'ZopePTK', which contain subdirectories:

      - PTKBase

      - PTKDemo

      - ZCallable

Copy or link each of these subdirectories into the Products directory of your Zope server, e.g.:

      $ cd /usr/local/Zope2/lib/python/Products
      $ mv /tmp/ZopePTK-x.x.x-src/PTKBase .
      $ mv /tmp/ZopePTK-x.x.x-src/PTKDemo .
      $ mv /tmp/ZopePTK-x.x.x-src/ZCallable .

Verify filesystem products
Start or restart your Zope server. Check to see that the following products are present in the Control_Panel / Products list; each should show a "normal" (non-broken) icon, and should have a version number matching the release version of the snapshot:
- PTKBase
- PTKDemo
- ZCallable
Create a portal
From the management interface, somewhere in the "main" section of your site (not the Control_Panel!), select "Portal (New)" from the add list. Fill out the constructor form, and click the "Add" button.

Refreshing your Checkout

Note that to refresh an existing CVS sandbox, you should use cvs up -d -P (assuming you want to remove obsolete directories and retrieve any newly-added ones).

*N.B.: Sites which have customized DemoPortal or Wizard should not copy the new DemoPortal or Wizard folders from the CVS sandbox to the Products directory -- doing so will replace you through-the-web changes!*

Fetching a Previous Version

[1] A normal CVS checkout retrieves what is called the "head" (the latest revision for each file) from the "main trunk" (no unmerged branches).

Retrieving Sources for a Release

Sources for prior releases are tagged, using the release version identifier, but with the periods replaced with underscores. For instance, version 0.8.1 of the PTK was tagged as ZopePTK-0_8_1-src. To fetch such a release from CVS:

    $ cvs -d :pserver:[email protected]:/cvs-repository checkout -r ZopePTK-0_8_1-src ZopePTK