[Asterisk-doc] docs installation.xml,1.20,1.21

blitzrage asterisk-doc@lists.digium.com
Wed, 21 Jul 2004 02:34:30 +0000


Comments:
Update of /cvsroot/asterisk/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27307/docs

Modified Files:
	installation.xml 
Log Message:
blitzrage
- remove stable and development sections and replace with Asterisk RC1
- add information regarding how to grab sources with CVSup
Index: installation.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/installation.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -C2 -d -r1.20 -r1.21
*** installation.xml	14 Jul 2004 16:27:28 -0000	1.20
--- installation.xml	21 Jul 2004 02:34:22 -0000	1.21
***************
*** 180,184 ****
  		</sect2>
  		
! 		<sect2>
  			<title>The Asterisk "Versioning" Issues</title>
  			<para>
--- 180,184 ----
  		</sect2>
  		
! <!--		<sect2>
  			<title>The Asterisk "Versioning" Issues</title>
  			<para>
***************
*** 190,193 ****
--- 190,194 ----
  			</para>
  		</sect2>
+ -->
  		
  		<sect2>
***************
*** 205,214 ****
  			<title>Getting the files from CVS</title>
  			<para>
! 			Once you've decided which branch you are going to download, you can use the following commands to retrieve 
! 			the sources.  Your server will download all the appropriate files from the CVS server
! 			and place them in their respective directories.  If you don't need zaptel or libpri
! 			simply leave them out of the checkout statement.
  			</para>
! 			<sect3>
  				<title>Development Branch</title>
  				<literallayout>
--- 206,215 ----
  			<title>Getting the files from CVS</title>
  			<para>
! 			The following commands can be used to retrieve the sourcecode.  Your server 
! 			will download all the appropriate files from the CVS server and place them 
! 			in their respective directories.  If you don't need zaptel or libpri simply 
! 			leave them out of the checkout statement.
  			</para>
! <!--			<sect3>
  				<title>Development Branch</title>
  				<literallayout>
***************
*** 228,233 ****
--- 229,271 ----
  					<command>cvs checkout -r v1-0_stable asterisk</command>
  				</literallayout>
+ 			</sect3> -->
+ 
+ 			<sect3>
+ 				<title>Asterisk v1.0 RC1</title>
+ 				<literallayout>
+ 					<command>cd /usr/src</command>
+ 					<command>export CVSROOT=:pserver:anoncvs@digium.com:/usr/cvsroot</command>
+ 					<command>cvs login</command> - the password is <emphasis>anoncvs</emphasis>
+ 					<command>cvs checkout asterisk libpri zaptel</command>
+ 				</literallayout>
  			</sect3>
  		</sect2>
+ 
+ 		<sect2>
+ 			<title>Getting the files using CVSup</title>
+ 			<para>
+ 			In order to get Asterisk using CVSup, create a file containing the following
+ 			information. You can call the file anything you want such as "asterisk-sup".
+ 			Place this file in your <filename class='directory'>/usr/src/</filename>
+ 			directory.
+ 			</para>
+ 			
+ 			<literallayout>
+ 			*default host=cvs.digium.com
+ 			*default base=/usr/src/
+ 			*default release=cvs tag=.
+ 			*default delete use-rel-suffix
+ 			asterisk
+ 			libpri
+ 			zaptel
+ 			</literallayout>
+ 
+ 			<para>
+ 			Once you have create the file, change to the <filename class='directory'>
+ 			/usr/src/</filename> directory and issue the <command>cvsup asterisk-sup</command>
+ 			command.
+ 			</para>
+ 		</sect2>
+ 
  		
  		<sect2>
***************
*** 235,239 ****
  			<para>
  			Updating Asterisk from CVS is relatively straight forward.  One note however
! 			is that the asterisk directory has a script to automatically update from CVS, compile
  			and install for you.  The only problem is that it doesn't do zaptel and libpri, 
  			so those will need to be done manually.  Before attempting to unload the modules
--- 273,277 ----
  			<para>
  			Updating Asterisk from CVS is relatively straight forward.  One note however
! 			is that the Asterisk directory has a script to automatically update from CVS, compile
  			and install for you.  The only problem is that it doesn't do zaptel and libpri, 
  			so those will need to be done manually.  Before attempting to unload the modules