All OpenACS code is available anonymously. To get code
anonymously, use the parameter -d:pserver:anonymous\@cvs.openacs.org:/cvsroot
immediately after cvs in a cvs
command to check out or export code.
If you are an OpenACS developer, you should check out code so @@ -81,24 +81,24 @@
If you are actively developing a non-core package, you should work from the latest core release branch. Currently this is -oacs-5-7. This ensures that you are working on top of a stable +oacs-5-9. This ensures that you are working on top of a stable OpenACS core, but still allows you to commit feature changes to -non-core packages. To check out all packages,
cvs -d :ext:cvs.openacs.org:/cvsroot co -r oacs-5-7 openacs-4If you work in the directories created with this command, all of -your cvs updates and commits will be confined to the oacs-5-7 +non-core packages. To check out all packages,
cvs -d :ext:cvs.openacs.org:/cvsroot co -r oacs-5-9 openacs-4If you work in the directories created with this command, all of +your cvs updates and commits will be confined to the oacs-5-9 branch. Your work will be merged back to HEAD for you with each release.
Because the entire openacs-4 directory is large, you may want to use only acs-core plus some specific modules. To do this, check out -core first:
cvs -d:ext:cvs.openacs.org:/cvsroot -r oacs-5-7 checkout acs-coreThen add modules as needed:
cd /var/lib/aolserver/service0/packages
+core first:cvs -d:ext:cvs.openacs.org:/cvsroot -r oacs-5-9 checkout acs-coreThen add modules as needed:
cd /var/lib/aolserver/service0/packages
cvs up -d packagename
... where packagename is the name of the package
you want. Visit the Package Inventory
and Package maintainers and status for a list of available
packages and their current state.
If you are actively developing packages in the OpenACS Core,
work from the HEAD branch. HEAD is used for active development of
the next version of core OpenACS. It may be very buggy; it may not
even install correctly. Do not use this branch for development of
@@ -107,16 +107,16 @@
developer account:
cvs -d:ext:cvs.openacs.org:/cvsroot checkout acs-coreTo check out HEAD anonymously:
cvs -d:pserver:anonymous\@cvs.openacs.org:/cvsroot checkout acs-core
.LRN consists of a given version openacs core, plus a set of
packages. These are collectively packages together to form a
distrubution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0.
.LRN also uses an OpenACS install.xml file during installation;
this file is distributed within the dotlrn package and must be
moved. To get a development checkout of .LRN in the subdirectory
-dotlrn:
cvs -d :pserver:anonymous\@cvs.openacs.org:/cvsroot checkout -r oacs-5-7 acs-core
+dotlrn:cvs -d :pserver:anonymous\@cvs.openacs.org:/cvsroot checkout -r oacs-5-9 acs-core
mv openacs-4 dotlrn
cd dotlrn/packages
-cvs -d :pserver:anonymous\@cvs.openacs.org:/cvsroot checkout -r oacs-5-7 dotlrn-all
+cvs -d :pserver:anonymous\@cvs.openacs.org:/cvsroot checkout -r oacs-5-9 dotlrn-all
mv dotlrn/install.xml ..
All OpenACS code resides within a single CVS module,
openacs-4. (The openacs-4
directory contains code for all versions of OpenACS 4 and later,
and .LRN 1 and later.) Checking out this module retrieves all
@@ -169,7 +169,7 @@
module of the same name.
Tags and Branches look similar in commands, but behave
differently. A tag is a fixed point on a branch. Check out a tag to
get a specific version of OpenACS. Check out a branch to get the
most current code for that major-minor version (e.g., 5.0.x or
@@ -412,7 +412,7 @@
Informal guidelines which may be obsolete in places and should
be reviewed:
Before committing to cvs you must submit a bug report and patch
to the OpenACS bug