[Asterisk-doc] docs installation.xml,1.4,1.5
blitzrage
asterisk-doc@lists.digium.com
Thu, 6 May 2004 17:46:07 +0000
Comments:
Update of /cvsroot/asterisk/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16992/docs
Modified Files:
installation.xml
Log Message:
blitzrage
- more updates to how to install. Updated what CVS is, how it works, why there are
two branches and how to retrieve them from Digium's CVS server.
Index: installation.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/installation.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** installation.xml 6 May 2004 14:37:45 -0000 1.4
--- installation.xml 6 May 2004 17:46:01 -0000 1.5
***************
*** 150,161 ****
<sect2>
<title>What is CVS?</title>
! <para>[CVS allows you to "check out" the latest version of a developer's code.]</para>
</sect2>
<sect2>
<title>The Asterisk "Versioning" Issues</title>
<para>
! [Stable releases seem to be few and far between, so CVS
! might work better for you... It's not perfect, but it's about
! the best you can hope for.]
</para>
</sect2>
--- 150,171 ----
<sect2>
<title>What is CVS?</title>
! <para>
! CVS is a central repository which developers use to control the source code. When a change is made
! it is committed to the CVS server where it is immediately available for download and compilation.
! Another added benefit to using CVS is that if something was working at one point, but a change causes
! it to break, the version for any particular file can be rolled back to a certain point. This is true
! for the entire tree as well. If you find something was working at one point but installing the latest
! version of Asterisk causes that to break, you can "roll-back" to any point in time (see Getting the
! files from CVS).
! </para>
</sect2>
<sect2>
<title>The Asterisk "Versioning" Issues</title>
<para>
! Asterisk comes in two flavours: Stable and Development. The stable branch contains code which is
! considered to be stable. The development branch is used for the testing and implementation of new
! features and is not meant to be used in a production environment. Basically the stable branch
! can be used for day to day use and development is used for the testing of new features which will
! eventually be seen in the stable branch.
</para>
</sect2>
***************
*** 163,170 ****
<title>Your Initial Download</title>
<para>
! The most common way that people get Asterisk is through CVS. There
! are stable release builds every once in a while, but they become outdated quite quickly.
! Your best bet is to get Asterisk from the Digium CVS server and compile it
! on your box.
</para>
<!-- removed distribution specific stuff -->
--- 173,180 ----
<title>Your Initial Download</title>
<para>
! Asterisk can be obtained from the Digium CVS server. You will require any packages which your distribution
! requires to download the sourcecode and to compile. Most modern Linux distributions have a category at installation
! for development tools, but some may vary. Binaries are available, however they are created on a *non-regular* basis,
! so you are best to stick to using the CVS method to obtain and compile the sourcecode.
</para>
<!-- removed distribution specific stuff -->
***************
*** 173,187 ****
<title>Getting the files from CVS</title>
<para>
! <literallayout>
! <command>cd /usr/src</command>
! <command>cvs -z3 -d:pserver:anoncvs@cvs.digium.com:/usr/cvsroot login</command>
! The password is <emphasis>anoncvs</emphasis>
! <command>cvs -z3 -d:pserver:anoncvs@cvs.digium.com:/usr/cvsroot checkout zaptel libpri asterisk</command>
! </literallayout>
</para>
! <para>
Your server will download all the appropriate files from the CVS server
! and place them in their respective directories.
! </para>
</sect2>
<sect2>
--- 183,218 ----
<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>
! <para>
! <literallayout>
! <command>cd /usr/src</command>
! <command>export CVSROOT=:pserver:anoncvs@cvs.digium.com:/usr/cvsroot</command>
! <command>cvs login</command> - The password is <emphasis>anoncvs</emphasis>
! <command>cvs checkout zaptel libpri asterisk</command>
! </literallayout>
! </para>
! <para>
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>
! <sect3>
! <title>Stable Branch</title>
! <para>
! <literallayout>
! <command>cd /usr/src</command>
! <command>export CVSROOT=:pserver:anoncvs@cvs.digium.com:/usr/cvsroot</command>
! <command>cvs login</command> - The password is <emphasis>anoncvs</emphasis>
! <command>cvs checkout -r v1-0_stable asterisk</command>
! </literallayout>
! </para>
! </sect3>
</sect2>
<sect2>
***************
*** 190,194 ****
To update your packages 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 for you,
so those will need to be done manually.
</para>
--- 221,225 ----
To update your packages 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.
</para>