| Prev | Part�III.�For OpenACS Package Developers | Next |
|---|
Check out the cvs tree. The files must be checked out +
Check out the cvs tree. The files must be checked out through a cvs account with write access. In this example, the cvs user on openacs.org is implied from the ssh login information previously set up. It could be overridden via foobar@openacs.org.
@@ -19,10 +19,10 @@
Make the tarball
openacs-core.�
Go to a new working space and export the tagged files.
mkdir /tmp/tarball
cd /tmp/tarball
-cvs -d :pserver:anonymous@openacs.org:/cvsroot export -r openacs-5-0-0a1 -d openacs acs-core
+cvs -d :pserver:anonymous@openacs.org:/cvsroot export -r openacs-5-0-0a1 acs-core
+mv openacs-4 openacs
Generate the tarball
cd /tmp/tarball
-rm -rf /tmp/tarball/openacs/CVS
tar cz -f openacs-5.0.0a1.tar.gz openacs
dotlrn.�
Go to a new working space and export the tagged files. (was getting errors here trying to use -d, so @@ -42,9 +42,8 @@
Copy the dotlrn install.xml file, which controls which packages are installed on setup, to the root location:
-cp /tmp/dotlrn-tarball/openacs-4/packages/dotlrn/install.xml /tmp/dotlrn-tarball/openacs
+cp /tmp/dotlrn-tarball/openacs/packages/dotlrn/install.xml /tmp/dotlrn-tarball/openacs
Generate the tarball
cd /tmp/tarball
-rm -rf /tmp/tarball/openacs-4/CVS
tar cz -f dotlrn-2.0.0a1.tar.gz openacs
Test the new tarball
Update on the site