svn: pear/peardoc/trunk/entities/ rs/group.xml rs/installation/cvs.xml rs/installation/svn.xml rs/installation.xml rs/standards.xml developers/contributing.xml developers/documentation.xml newmaint/takingover.xml users/commandline/installing.xml users/installation/cvs.xml users/installation/svn.xml global.ent

Modified: pear/peardoc/trunk/en/chapters/group.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/group.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/chapters/group.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -47,7 +47,7 @@
        <literal>Name</literal> refers to the last part of the
        <literal>The_Package_Name</literal>, all subclasses of the main
        class, should be put in there or subdirectories of it. You can
-       refer to http://cvs.php.net/cvs.php/pear/Cache_Lite/ - the
+       refer to http://svn.php.net/viewvc/pear/packages/Cache_Lite/trunk/ - the
        directory <literal>Lite</literal> as an example (this basically
        documents what we currently do anyway).
      </para>

Deleted: pear/peardoc/trunk/en/chapters/installation/cvs.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/installation/cvs.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/chapters/installation/cvs.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -1,85 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="installation.cvs"><info><title>CVS installer</title></info>
-
-
-   <para>
-	This passage will describe how to install the latest development
-	version of a PEAR package from CVS.
-   </para>
-   <para>
-    It is NOT recommended to run a package from CVS in working environments!
-    Because CVS versions are not regular releases, this means:
-    <itemizedlist>
-     <listitem>
-      <simpara>You could get no kind of help from the maintainer or anybody other.</simpara>
-     </listitem>
-     <listitem>
-      <simpara>Versions in CVS may break the upgrade mechanism of the PEAR Installer.</simpara>
-     </listitem>
-    </itemizedlist>
-   </para>
-   <para>
-    You should use a package from CVS only, if:
-    <itemizedlist>
-     <listitem>
-      <simpara>The maintainer recommended it for you.</simpara>
-     </listitem>
-     <listitem>
-      <simpara>You want to help in development of a package.</simpara>
-     </listitem>
-     <listitem>
-      <simpara>You really need a special patch or function, which is not currently released.</simpara>
-     </listitem>
-    </itemizedlist>
-   </para>
-   <para>
-    If you still want to install a package from CVS, you have to do the same steps
-    like a package maintainer creating a new release of a package. If you have problems
-    following the next steps, take a look into the
-    <link linkend="guide-developers">Developers Section</link> of the manual.
-   </para>
-   <orderedlist>
-    <listitem>
-     <para>
-      Get the package files from CVS like described in <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.anoncvs;">&url.php.anoncvs;</link>
-     </para>
-     <para>
-      The name of the module to checkout is <filename>pear/&lt;packagename&gt;</filename>,
-      i.e. <command> cvs -d :pserver:[email protected]:/repository checkout pear/HTTP_Client</command>.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Check the <filename>package.xml</filename> file, especially the dir and file entries.
-      They must match the existing files and directory structure. If they differ, contact
-      the package maintainer and ask for an update of the <filename>package.xml</filename>.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Create a valid package using the PEAR Installer
-      <command>pear package &lt;path to package.xml&gt;</command>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      If you have already installed the package: remove it to avoid version conflicts:
-      <command>pear uninstall &lt;package&gt;</command>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Install your package archive:
-      <command>pear install &lt;package-file&gt;</command>
-     </para>
-     <para>
-      Now, you have a CVS version installed!
-     </para>
-    </listitem>
-   </orderedlist>
-   <para>
-    You should upgrade to an official release of the package as early as possible.
-    Before you install the official release, uninstall the CVS version to avoid
-    version conflicts.
-   </para>
-  </section>

Copied: pear/peardoc/trunk/en/chapters/installation/svn.xml (from rev 284165, pear/peardoc/trunk/en/chapters/installation/cvs.xml)
===================================================================
--- pear/peardoc/trunk/en/chapters/installation/svn.xml	                        (rev 0)
+++ pear/peardoc/trunk/en/chapters/installation/svn.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="utf-8"?>
+<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="installation.cvs"><info><title>CVS installer</title></info>
+
+
+   <para>
+	This passage will describe how to install the latest development
+	version of a PEAR package from SVN.
+   </para>
+   <para>
+    It is NOT recommended to run a package from SVN in working environments!
+    Because CVS versions are not regular releases, this means:
+    <itemizedlist>
+     <listitem>
+      <simpara>You could get no kind of help from the maintainer or anybody other.</simpara>
+     </listitem>
+     <listitem>
+      <simpara>Versions in SVN may break the upgrade mechanism of the PEAR Installer.</simpara>
+     </listitem>
+    </itemizedlist>
+   </para>
+   <para>
+    You should use a package from SVN only, if:
+    <itemizedlist>
+     <listitem>
+      <simpara>The maintainer recommended it for you.</simpara>
+     </listitem>
+     <listitem>
+      <simpara>You want to help in development of a package.</simpara>
+     </listitem>
+     <listitem>
+      <simpara>You really need a special patch or function, which is not currently released.</simpara>
+     </listitem>
+    </itemizedlist>
+   </para>
+   <para>
+    If you still want to install a package from SVN, you have to do the same steps
+    like a package maintainer creating a new release of a package. If you have problems
+    following the next steps, take a look into the
+    <link linkend="guide-developers">Developers Section</link> of the manual.
+   </para>
+   <orderedlist>
+    <listitem>
+     <para>
+      Get the package files from SVN like described in <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.anoncvs;">&url.php.anonsvn;</link>
+     </para>
+     <para>
+      The name of the module to checkout is <filename>pear/packages/&lt;packagename&gt;/trunk</filename>,
+      i.e. <command> svn checkout http://svn.php.net/repository/pear/packages/HTTP_Client/trunk</command>.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Check the <filename>package.xml</filename> file, especially the dir and file entries.
+      They must match the existing files and directory structure. If they differ, contact
+      the package maintainer and ask for an update of the <filename>package.xml</filename>.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Create a valid package using the PEAR Installer
+      <command>pear package &lt;path to package.xml&gt;</command>
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      If you have already installed the package: remove it to avoid version conflicts:
+      <command>pear uninstall &lt;package&gt;</command>
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Install your package archive:
+      <command>pear install &lt;package-file&gt;</command>
+     </para>
+     <para>
+      Now, you have a SVN version installed!
+     </para>
+    </listitem>
+   </orderedlist>
+   <para>
+    You should upgrade to an official release of the package as early as possible.
+    Before you install the official release, uninstall the CVS version to avoid
+    version conflicts.
+   </para>
+  </section>


Property changes on: pear/peardoc/trunk/en/chapters/installation/svn.xml
___________________________________________________________________
Added: cvs2svn:cvs-rev
   + 1.4
Added: svn:keywords
   + Id Revision Rev

Modified: pear/peardoc/trunk/en/chapters/installation.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/installation.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/chapters/installation.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -14,6 +14,6 @@
   &chapters.installation.cli;
   &chapters.installation.shared;
   &chapters.installation.manually;
-  &chapters.installation.cvs;
+  &chapters.installation.svn;
   &chapters.installation.pecl;
  </chapter>

Modified: pear/peardoc/trunk/en/chapters/standards.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/standards.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/chapters/standards.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -888,13 +888,13 @@

   </section>

-  <section xml:id="standards.cvs"><info><title>Using CVS</title></info>
+  <section xml:id="standards.svn"><info><title>Using SVN</title></info>

    <simpara>
-    This section applies only to packages using CVS at cvs.php.net.
+    This section applies only to packages using SVN at svn.php.net.
    </simpara>
    <para>
-    Include the &dollar;Id&dollar; CVS keyword in each file.
+    Include the &dollar;Id&dollar; SVN keyword in each file.
 <!--
     <note>
      <simpara>
@@ -908,12 +908,12 @@
    </para>
    <para>
     The rest of this section assumes that you have basic knowledge
-    about CVS tags and branches.
+    about SVN tags and branches.
    </para>
    <para>
-    CVS tags are used to label which revisions of the files in your
+    SVN tags are used to label which revisions of the files in your
     package belong to a given release.  Below is a list of the
-    required and suggested CVS tags:
+    required and suggested SVN tags:

     <variablelist>
      <varlistentry>
@@ -958,13 +958,9 @@
     Below is an example of how to tag the 1.2.0 release of the
     <classname>Money_Fast</classname> package:
     <informalexample>
-     <screen><prompt>$ </prompt><command>cd pear/Money_Fast</command>
-<prompt>$ </prompt><command>cvs tag RELEASE_1_2_0</command>
-<computeroutput>T Fast.php
-T README
-T package.xml
-</computeroutput>
-</screen>
+     <screen>
+      <prompt>$ </prompt><command>SVN copy http://svn.php.net/repository/pear/packages/Money_Fast/trunk  http://svn.php.net/repository/pear/packages/Money_Fast/tags/RELEASE_1_2_0</command>
+     </screen>
     </informalexample>
     By doing this you make it possible for the PEAR web site to take
     you through the rest of your release process.
@@ -972,20 +968,13 @@
    <para>
     Here's an example of how to create a QA branch:
     <informalexample>
-     <screen><prompt>$ </prompt><command>cvs tag QA_2_0_0_BP</command>
+     <screen><prompt>$ </prompt><command>svn copy http://svn.php.net/repository/pear/packages/Money_Fast/trunk http://svn.php.net/repository/pear/packages/Money_Fast/branches/QA_2_0_0</command>
 ...
-<prompt>$ </prompt><command>cvs rtag -b -r QA_2_0_0_BP QA_2_0_0</command>
-<prompt>$ </prompt><command>cvs update -r QA_2_0_0</command>
-<prompt>$ </prompt><command>cvs tag RELEASE_2_0_0RC1</command>
+<prompt>$ </prompt><command>svn copy http://svn.php.net/repository/pear/packages/Money_Fast/branches/QA_2_0_0 http://svn.php.net/repository/pear/packages/Money_Fast/tags/RELEASE_2_0_0RC1</command>
 ...and then the actual release, from the same branch:
-<prompt>$ </prompt><command>cvs tag RELEASE_2_0_0</command>
+<prompt>$ </prompt><command>svn copy http://svn.php.net/repository/pear/packages/Money_Fast/branches/QA_2_0_0 http://svn.php.net/repository/pear/packages/Money_Fast/tags/RELEASE_2_0_0</command>
 </screen>
     </informalexample>
-    The <literal>QA_2_0_0_BP</literal> tag is a
-    <quote>branch point</quote> tag, which is the start
-    point of the tag.  It's always a good idea to start a CVS branch
-    from such branch points.  MAINT branches may use the RELEASE tag
-    as their branch point.
    </para>
   </section>


Modified: pear/peardoc/trunk/en/guide/developers/contributing.xml
===================================================================
--- pear/peardoc/trunk/en/guide/developers/contributing.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/guide/developers/contributing.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -67,12 +67,12 @@
          The latest revision of the package's source code has to be
          available in a public <acronym>SCM</acronym>
          (Source Code Management) system such as the
-         <acronym>CVS</acronym> server at
-         <literal>cvs.php.net</literal>, the Subversion repository
+         <acronym>SVN</acronym> server at
+         <literal>svn.php.net</literal>, the Subversion repository
          of <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.google.code;">Google Code</link>, or
          at sites such as <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.sourceforge;">SourceForge</link>.  Hosting at
          Google Code or SourceForge is freely available under their terms
-         of use at any time.  Write access to cvs.php.net is available
+         of use at any time.  Write access to svn.php.net is available
          once the package has been accepted as a PEAR package.
        </para>
        <para>
@@ -345,9 +345,9 @@
          <para>
           If you want to administrate your code via
           <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.cvs;">CVS</link> , you can also
-          apply for a CVS account to have access to the pear
-          <abbrev>CVS</abbrev> module on <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.cvs;">
-          cvs.php.net</link>. This makes it easier for other users
+          apply for a SVN account to have access to the pear
+          <abbrev>SVN</abbrev> module on <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.cvs;">
+          svn.php.net</link>. This makes it easier for other users
           to contribute to your code. The PHP Group ([email protected]) manage
           the PHP CVS server, which is used for maintaining PEAR packages.
           If you already have a PHP CVS account you will ask the

Modified: pear/peardoc/trunk/en/guide/developers/documentation.xml
===================================================================
--- pear/peardoc/trunk/en/guide/developers/documentation.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/guide/developers/documentation.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -40,21 +40,20 @@
     <title>Obtaining the manual sources</title>

     <para>The Docbook XML sources of the documentation are hosted on php.net's
-    CVS server in the <literal>peardoc</literal> module.</para>
+    SVN server in the <literal>peardoc</literal> module.</para>

     <para>The checkout process is relatively simple:</para>

-    <screen><![CDATA[$ cvs -d :pserver:&lt;user&gt;@cvs.php.net:/repository login
-[password]
-$ cvs -d :pserver:&lt;user&gt;@cvs.php.net:/repository co
-peardoc]]></screen>
+    <screen><![CDATA[
+    $ svn checkout http://svn.php.net:/repository/pear/peardoc/trunk
+    ]]></screen>

     <para>Details about this process as well as anonymous login data can be
-    found on <link xlink:href="&url.php.anoncvs;">php.net's CVS
+    found on <link xlink:href="&url.php.anonsvn;">php.net's SVN
     page</link>.</para>

     <note>
-      <para>You need rights for the <literal>peardoc</literal> CVS module to
+      <para>You need rights for the <literal>peardoc</literal> SVN module to
       be able to commit. Along with pear karma, every developer should have
       gotten the appropriate rights to <literal>peardoc</literal>. This is how
       it should be in theory, but one will probably have to send a mail to

Modified: pear/peardoc/trunk/en/guide/newmaint/takingover.xml
===================================================================
--- pear/peardoc/trunk/en/guide/newmaint/takingover.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/guide/newmaint/takingover.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -49,8 +49,8 @@

       <note>
         <simpara>
-          If you already have a CVS account for
-          <literal>cvs.php.net</literal>, it is only necessary for you
+          If you already have a SVN account for
+          <literal>svn.php.net</literal>, it is only necessary for you
           to get additional <quote>karma</quote> for the module where
           the package resides.  You can request this karma by sending an
           email to the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="mailto:&email.pear.group;">PEAR

Modified: pear/peardoc/trunk/en/guide/users/commandline/installing.xml
===================================================================
--- pear/peardoc/trunk/en/guide/users/commandline/installing.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/guide/users/commandline/installing.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -211,14 +211,14 @@
    </section>


-   <section xml:id="guide.users.commandline.installing.cvs"><info><title>Installing packages from CVS</title></info>
+   <section xml:id="guide.users.commandline.installing.cvs"><info><title>Installing packages from SVN</title></info>


     <para>This passage will describe how to install the latest development
-    version of a PEAR package from CVS.</para>
+    version of a PEAR package from SVN.</para>

-    <para>It is NOT recommended to run a package from CVS in working
-    environments! Because CVS versions are not regular releases, this means:
+    <para>It is NOT recommended to run a package from SVN in working
+    environments! Because SVN versions are not regular releases, this means:
     <itemizedlist>
         <listitem>
           <simpara>You could get no kind of help from the maintainer or
@@ -226,12 +226,12 @@
         </listitem>

         <listitem>
-          <simpara>Versions in CVS may break the upgrade mechanism of the PEAR
+          <simpara>Versions in SVN may break the upgrade mechanism of the PEAR
           Installer.</simpara>
         </listitem>
       </itemizedlist></para>

-    <para>You should use a package from CVS only, if: <itemizedlist>
+    <para>You should use a package from SVN only, if: <itemizedlist>
         <listitem>
           <simpara>The maintainer recommended it for you.</simpara>
         </listitem>
@@ -246,18 +246,17 @@
         </listitem>
       </itemizedlist></para>

-    <para>If you still want to install a package from CVS, you have to do the
+    <para>If you still want to install a package from SVN, you have to do the
     same steps like a package maintainer creating a new release of a package.
     If you have problems following the next steps, take a look into the <link linkend="guide-developers">Developers Section</link> of the manual.</para>

     <orderedlist>
       <listitem>
-        <para>Get the package files from CVS like described in <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.anoncvs;">&url.php.anoncvs;</link></para>
+        <para>Get the package files from SVN like described in <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.anonsvn;">&url.php.anonsvn;</link></para>

         <para>The name of the module to checkout is
-        <filename>pear/&lt;packagename&gt;</filename>, i.e. <command> cvs -d
-        :pserver:[email protected]:/repository checkout
-        pear/HTTP_Client</command>.</para>
+        <filename>pear/&lt;packagename&gt;/trunk</filename>, i.e.
+        <command> svn checkout http://svn.php.net/repository/pear/packages/HTTP_Client/trunk HTTP_Client</command>.</para>
       </listitem>

       <listitem>
@@ -282,12 +281,12 @@
         <para>Install your package archive: <command>pear install
         &lt;package-file&gt;</command></para>

-        <para>Now, you have a CVS version installed!</para>
+        <para>Now, you have a SVN version installed!</para>
       </listitem>
     </orderedlist>

     <para>You should upgrade to an official release of the package as early as
-    possible. Before you install the official release, uninstall the CVS
+    possible. Before you install the official release, uninstall the SVN
     version to avoid version conflicts.</para>
    </section>


Deleted: pear/peardoc/trunk/en/guide/users/installation/cvs.xml
===================================================================
--- pear/peardoc/trunk/en/guide/users/installation/cvs.xml	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/en/guide/users/installation/cvs.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -1,85 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="installation.cvs"><info><title>CVS installer</title></info>
-
-
-   <para>
-	This passage will describe how to install the latest development
-	version of a PEAR package from CVS.
-   </para>
-   <para>
-    It is NOT recommended to run a package from CVS in working environments!
-    Because CVS versions are not regular releases, this means:
-    <itemizedlist>
-     <listitem>
-      <simpara>You could get no kind of help from the maintainer or anybody other.</simpara>
-     </listitem>
-     <listitem>
-      <simpara>Versions in CVS may break the upgrade mechanism of the PEAR Installer.</simpara>
-     </listitem>
-    </itemizedlist>
-   </para>
-   <para>
-    You should use a package from CVS only, if:
-    <itemizedlist>
-     <listitem>
-      <simpara>The maintainer recommended it for you.</simpara>
-     </listitem>
-     <listitem>
-      <simpara>You want to help in development of a package.</simpara>
-     </listitem>
-     <listitem>
-      <simpara>You really need a special patch or function, which is not currently released.</simpara>
-     </listitem>
-    </itemizedlist>
-   </para>
-   <para>
-    If you still want to install a package from CVS, you have to do the same steps
-    like a package maintainer creating a new release of a package. If you have problems
-    following the next steps, take a look into the
-    <link linkend="guide-developers">Developers Section</link> of the manual.
-   </para>
-   <orderedlist>
-    <listitem>
-     <para>
-      Get the package files from CVS like described in <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.anoncvs;">&url.php.anoncvs;</link>
-     </para>
-     <para>
-      The name of the module to checkout is <filename>pear/&lt;packagename&gt;</filename>,
-      i.e. <command> cvs -d :pserver:[email protected]:/repository checkout pear/HTTP_Client</command>.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Check the <filename>package.xml</filename> file, especially the dir and file entries.
-      They must match the existing files and directory structure. If they differ, contact
-      the package maintainer and ask for an update of the <filename>package.xml</filename>.
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Create a valid package using the PEAR Installer
-      <command>pear package &lt;path to package.xml&gt;</command>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      If you have already installed the package: remove it to avoid version conflicts:
-      <command>pear uninstall &lt;package&gt;</command>
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      Install your package archive:
-      <command>pear install &lt;package-file&gt;</command>
-     </para>
-     <para>
-      Now, you have a CVS version installed!
-     </para>
-    </listitem>
-   </orderedlist>
-   <para>
-    You should upgrade to an official release of the package as early as possible.
-    Before you install the official release, uninstall the CVS version to avoid
-    version conflicts.
-   </para>
-  </section>

Copied: pear/peardoc/trunk/en/guide/users/installation/svn.xml (from rev 284165, pear/peardoc/trunk/en/guide/users/installation/cvs.xml)
===================================================================
--- pear/peardoc/trunk/en/guide/users/installation/svn.xml	                        (rev 0)
+++ pear/peardoc/trunk/en/guide/users/installation/svn.xml	2009-07-16 02:04:19 UTC (rev 284168)
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="utf-8"?>
+<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="installation.cvs"><info><title>CVS installer</title></info>
+
+
+   <para>
+	This passage will describe how to install the latest development
+	version of a PEAR package from SVN.
+   </para>
+   <para>
+    It is NOT recommended to run a package from SVN in working environments!
+    Because SVN versions are not regular releases, this means:
+    <itemizedlist>
+     <listitem>
+      <simpara>You could get no kind of help from the maintainer or anybody other.</simpara>
+     </listitem>
+     <listitem>
+      <simpara>Versions in SVN may break the upgrade mechanism of the PEAR Installer.</simpara>
+     </listitem>
+    </itemizedlist>
+   </para>
+   <para>
+    You should use a package from SVN only, if:
+    <itemizedlist>
+     <listitem>
+      <simpara>The maintainer recommended it for you.</simpara>
+     </listitem>
+     <listitem>
+      <simpara>You want to help in development of a package.</simpara>
+     </listitem>
+     <listitem>
+      <simpara>You really need a special patch or function, which is not currently released.</simpara>
+     </listitem>
+    </itemizedlist>
+   </para>
+   <para>
+    If you still want to install a package from SVN, you have to do the same steps
+    like a package maintainer creating a new release of a package. If you have problems
+    following the next steps, take a look into the
+    <link linkend="guide-developers">Developers Section</link> of the manual.
+   </para>
+   <orderedlist>
+    <listitem>
+     <para>
+      Get the package files from SVN like described in <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.anonsvn;">&url.php.anonsvn;</link>
+     </para>
+     <para>
+      The name of the module to checkout is <filename>pear/&lt;packagename&gt;/trunk</filename>,
+      i.e. <command> svn checkout http://svn.php.net/repository/pear/packages/HTTP_Client/trunk HTTP_Client</command>.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Check the <filename>package.xml</filename> file, especially the dir and file entries.
+      They must match the existing files and directory structure. If they differ, contact
+      the package maintainer and ask for an update of the <filename>package.xml</filename>.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Create a valid package using the PEAR Installer
+      <command>pear package &lt;path to package.xml&gt;</command>
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      If you have already installed the package: remove it to avoid version conflicts:
+      <command>pear uninstall &lt;package&gt;</command>
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Install your package archive:
+      <command>pear install &lt;package-file&gt;</command>
+     </para>
+     <para>
+      Now, you have a SVN version installed!
+     </para>
+    </listitem>
+   </orderedlist>
+   <para>
+    You should upgrade to an official release of the package as early as possible.
+    Before you install the official release, uninstall the SVN version to avoid
+    version conflicts.
+   </para>
+  </section>


Property changes on: pear/peardoc/trunk/en/guide/users/installation/svn.xml
___________________________________________________________________
Added: cvs2svn:cvs-rev
   + 1.3
Added: svn:keywords
   + Id Revision Rev

Modified: pear/peardoc/trunk/entities/global.ent
===================================================================
--- pear/peardoc/trunk/entities/global.ent	2009-07-16 01:45:38 UTC (rev 284167)
+++ pear/peardoc/trunk/entities/global.ent	2009-07-16 02:04:19 UTC (rev 284168)
@@ -135,6 +135,7 @@
 <!ENTITY url.php.cvs.pear 'http://cvs.php.net/pear/'>
 <!ENTITY url.php.cvs.peardoc.authoring 'http://cvs.php.net/cvs.php/peardoc/en/authoring/'>
 <!ENTITY url.php.cvs.new 'http://www.php.net/cvs-php.php'>
+<!ENTITY url.php.svn 'http://svn.php.net/'>
 <!ENTITY url.php.gtk 'http://gtk.php.net/'>
 <!ENTITY url.php.bugs 'http://bugs.php.net/'>
 <!ENTITY url.php.bugs.howto 'http://bugs.php.net/how-to-report.php'>