cvs: peardoc /en/guide/migrating channels.xml

From: Date: Fri, 25 Nov 2005 19:10:55 +0000
Subject: cvs: peardoc /en/guide/migrating channels.xml
Groups: php.pear.doc 
Request: Send a blank email to pear-doc+get-7209@lists.php.net to get a copy of this message
moosh Fri Nov 25 14:10:55 2005 EDT Modified files: /peardoc/en/guide/migrating channels.xml Log: - indent before initial translation http://cvs.php.net/diff.php/peardoc/en/guide/migrating/channels.xml?r1=1.2&r2=1.3&ty=u Index: peardoc/en/guide/migrating/channels.xml diff -u peardoc/en/guide/migrating/channels.xml:1.2 peardoc/en/guide/migrating/channels.xml:1.3 --- peardoc/en/guide/migrating/channels.xml:1.2 Sun Sep 18 01:36:01 2005 +++ peardoc/en/guide/migrating/channels.xml Fri Nov 25 14:10:52 2005 @@ -1,54 +1,69 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.2 $ --> - <chapter id="guide.migrating.channels"> - <chapterinfo> - <author> - <firstname>Gregory</firstname> - <surname>Beaver</surname> - </author> - <date>$Date: 2005/09/18 05:36:01 $</date> - </chapterinfo> - <title>Channels</title> - - <simpara> - PEAR Channels provide a robust and effective way of distributing development. The - addition of channel support to the PEAR installer as of version 1.4.0 means that it - is now simpler to distribute any PHP code project using the PEAR installer than it - ever was. PEAR Channels allow developers of applications to effectively depend upon - packages from pear.php.net and any other source that provides a channel server. For - users of these applications, this eliminates the complexity of installation and - configuration. Now, all the user will need to do is to type a single - <literal>pear install channel/Packagename</literal> command and go! - </simpara> +<!-- $Revision: 1.3 $ --> +<chapter id="guide.migrating.channels"> + <chapterinfo> + <author> + <firstname>Gregory</firstname> + <surname>Beaver</surname> + </author> + <date>$Date: 2005/11/25 19:10:52 $</date> + </chapterinfo> + <title>Channels</title> - <simpara> - Before PEAR 1.4.0, the only solution to depending on code from several sources is to - bundle the code. This has several bad side effects, the most obvious of which - is that code size increases dramatically, and makes upgrading for a minor bug - fix a complicated download for the user. - </simpara> + <simpara> + PEAR Channels provide a robust and effective way of distributing development. - <simpara> - Channels allow an application developer to depend on packages from pear.php.net, - a package from pear.example.com, and others. The user will only need to install/upgrade - from a single source using the pear installer. With the current state of affairs, the - pear installer is only really useful for installing, well, PEAR packages. Because of this - difficulty (among others), traditionally very few packages are available as PEAR packages - that can be installed with the PEAR installer. - </simpara> - - <simpara> - PEAR 1.4.0+ aims to eliminate this and other barriers to application development. + The addition of channel support to the PEAR installer as of version 1.4.0 + means that it is now simpler to distribute any PHP code project using the + PEAR installer than it ever was. + + PEAR Channels allow developers of applications to effectively depend upon + packages from pear.php.net + and any other source that provides a channel server. + + For users of these applications, + this eliminates the complexity of installation and configuration. + + Now, all the user will need to do is to type a single + <literal>pear install channel/Packagename</literal> + command and go! + </simpara> + + <simpara> + Before PEAR 1.4.0, the only solution to depending on code from several + sources is to bundle the code. + + This has several bad side effects, the most obvious of which is that code + size increases dramatically, and makes upgrading for a minor bug fix a + complicated download for the user. </simpara> - - <warning> - <title>Incomplete documentation</title> - <para>Documentation is not yet complete</para> - </warning> + + <simpara> + Channels allow an application developer to depend on packages + from pear.php.net, a package from pear.example.com, and others. + + The user will only need to install/upgrade from a single source using the + pear installer. - &guide.migrating.channels.xml; - &guide.migrating.channels.xmlrpcfunctions; - </chapter> + With the current state of affairs, the pear installer is only really useful + for installing, well, PEAR packages. + + Because of this difficulty (among others), traditionally very few packages + are available as PEAR packages that can be installed with the PEAR installer. + </simpara> + + <simpara> + PEAR 1.4.0+ aims to eliminate this and other barriers to application development. + </simpara> + + <warning> + <title>Incomplete documentation</title> + <para>Documentation is not yet complete</para> + </warning> + + &guide.migrating.channels.xml; + &guide.migrating.channels.xmlrpcfunctions; +</chapter> <!-- Keep this comment at the end of the file Local variables:

« previous php.pear.doc (#7209) next »