Index: openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml,v
diff -u -r1.16 -r1.17
--- openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml	11 Mar 2004 09:16:56 -0000	1.16
+++ openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml	14 May 2004 14:10:26 -0000	1.17
@@ -25,23 +25,23 @@
         <remark>.LRN: this must be repeated for .LRN modules (dotlrn-core in the dotlrn cvs tree) and for any modified modules in the .LRN prerequisites (dotlrn-prereq in openacs cvs tree).  My current working model is that I bulk-update .LRN and OpenACS core but that I don't touch dotlrn-prereq modules - I just use the most recent release and it's up to individual package developers to tag and <link linkend="releasing-package">release those packages</link> when they change.  This model is already broken because following it means that dotlrn-prereqs don't get new translations.</remark>
         <orderedlist>
           <listitem>
-            <para>Update /var/lib/aolserver/service0/packages/acs-core-docs/www/xml/variables.ent with the new version number.
+            <para>Update /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml/variables.ent with the new version number.
             </para>
           </listitem>
           <listitem>
-            <para>Add new section in /var/lib/aolserver/service0/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml
+            <para>Add new section in /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml
 </para>
           </listitem>
           <listitem>
             <para>Regenerate all HTML docs</para>
-            <screen>cd /var/lib/aolserver/service0/packages/acs-core-docs/www/xml
+            <screen>cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml
 make</screen>
           </listitem>
           <listitem>
-            <para>Update /var/lib/aolserver/service0/readme.txt with the new version number</para>
+            <para>Update /var/lib/aolserver/$OPENACS_SERVICE_NAME/readme.txt with the new version number</para>
           </listitem>
           <listitem>
-            <para>Update version number in all of the core packages.  Here's a bash/perl script which works but could be made easier to use.  Run it from /var/lib/aolserver/service0/packages:</para>
+            <para>Update version number in all of the core packages.  Here's a bash/perl script which works but could be made easier to use.  Run it from /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages:</para>
           <programlisting>#!/bin/sh
 # run this file from ../packages to renumber all .info version numbers
 
@@ -73,7 +73,7 @@
           <title>Rubuild the Changelog</title>
             <para>Rebuild the Changelog.  I use a tool called cvs2cl.  Run this command from the package root to automatically generate a Changelog file  in the same dir:</para>
         </formalpara>
-        <screen>cd /var/lib/aolserver/service0
+        <screen>cd /var/lib/aolserver/$OPENACS_SERVICE_NAME
 perl /var/tmp/cvs2cl/cvs2cl.pl -F oacs-5-0 --delta openacs-5-0-0-final:oacs-5-0</screen>
         <para>
           Commit changes
@@ -290,7 +290,7 @@
       </listitem>
       <listitem>
         <para>Tag the updated work.:</para>
-        <screen><action>cd /var/lib/aolserver/service0/packages/<replaceable>myfirstpackage</replaceable>
+        <screen><action>cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/<replaceable>myfirstpackage</replaceable>
 cvs tag <replaceable>myfirstpackages-1-0-0-final</replaceable>
 cvs tag -F <replaceable>openacs-5-0-compat</replaceable>
 </action></screen>