[Checkins] SVN: developer_docs/trunk/source/ updated

Andreas Jung andreas at andreas-jung.com
Thu Apr 2 23:59:10 EDT 2009


Log message for revision 98801:
  updated
  

Changed:
  A   developer_docs/trunk/source/cvs.rst
  U   developer_docs/trunk/source/index.rst
  U   developer_docs/trunk/source/subversion-writable-checkouts.rst

-=-
Added: developer_docs/trunk/source/cvs.rst
===================================================================
--- developer_docs/trunk/source/cvs.rst	                        (rev 0)
+++ developer_docs/trunk/source/cvs.rst	2009-04-03 03:59:09 UTC (rev 98801)
@@ -0,0 +1,55 @@
+CVS access
+----------
+
+.. note::
+
+   This document is only of importance if you are interested for checking
+   out older Zope 2 versions (before Zope 2.8). The current codebase
+   is now maintained in our Subversion repository
+  
+
+Anyone can track Zope changes with a read-only checkout of the sources - here
+are instructions for hooking it up.
+
+There are several top-level modules in the archives - chief among them is the
+Zope sources - we'll use them for our example.
+
+Read-only access is via CVS pserver mode.
+
+Before you can check anything out, you must have done a CVS "login" to the CVS
+pserver. You only need to login once per repository per account. To login::
+
+     >>> cvs -d :pserver:anonymous at cvs.zope.org:/cvs-repository login
+
+You will be prompted for a password - anything will satisfy the prompt,
+including an empty line.
+
+(In the command, The -d option identifies the repository, indicating pserver
+mode, user anonymous, host cvs.zope.org, and directory /cvs-repository.)
+
+You only need to log in once - it causes a file named .cvspass, with the login
+info, to be created in your home directory. All subsequent access to that
+repository will use the stashed info.
+
+Once your login is established, you can do your initial check out::
+
+    >>> cvs -z7 -d :pserver:anonymous at cvs.zope.org:/cvs-repository checkout Zope
+
+(-z7 says to use a substantial level of compression, balancing CPU and network
+bandwidth. Note It's Zope, no longer Zope2. The section is not maintained, and
+will eventually be removed.)
+
+This should issue lots of check out messages, creating a directory named Zope,
+with the entire distribution inside it. The initial checkout creates a copy of
+the source files together with some CVS bookkeeping, in directories all named
+CVS.
+
+Once you've done these initial steps, you can stay current by cd'ing into any
+of the created Zope subdirectories and typing:
+
+    >>> cvs -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. In a
+pinch, you could just do a cvs up, but: you won't get new directories, nor will
+defunct directories be removed, you'll get lots of unnecessary messages...)

Modified: developer_docs/trunk/source/index.rst
===================================================================
--- developer_docs/trunk/source/index.rst	2009-04-03 03:50:18 UTC (rev 98800)
+++ developer_docs/trunk/source/index.rst	2009-04-03 03:59:09 UTC (rev 98801)
@@ -22,7 +22,6 @@
    :maxdepth: 2
 
    becoming-a-contributor
-   contributor-faq
 
 
 Zope CVS Repository (obsolete)
@@ -31,5 +30,5 @@
 .. toctree::
    :maxdepth: 2
 
-   cvs-access
+   cvs
 

Modified: developer_docs/trunk/source/subversion-writable-checkouts.rst
===================================================================
--- developer_docs/trunk/source/subversion-writable-checkouts.rst	2009-04-03 03:50:18 UTC (rev 98800)
+++ developer_docs/trunk/source/subversion-writable-checkouts.rst	2009-04-03 03:59:09 UTC (rev 98801)
@@ -2,7 +2,7 @@
 ------------------
 
 Below are instructions for hooking up with our Public Subversion repository
-with checkin ability.  See the `Contributor documentation <contributor-faq.html>`_.
+with checkin ability.  
 
 Overview
 ########



More information about the Checkins mailing list