<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 11:15:01 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Pádraic Brady's Blog:Doing that thing called PEAR - Packaging Source Code for PEAR Distribution]]></title>
      <guid>http://www.phpdeveloper.org/news/8916</guid>
      <link>http://www.phpdeveloper.org/news/8916</link>
      <description><![CDATA[<i>Pádraic Brady</i> has followed up his <a href="http://blog.astrumfutura.com/archives/311-To-PEAR-or-not-to-PEAR-And-how-to-PEAR-anyway.html">last post on PEAR</a>. This time he's covered <a href="http://blog.astrumfutura.com/archives/312-Doing-that-thing-called-PEAR-Packaging-Source-Code-for-PEAR-Distribution.html">the method</a> to package and distribute source code using the <a href="http://pear.php.net/package/PEAR/">PEAR installer</a>.

<blockquote>All right then! You read the last blog entry advocating PEAR (or found it during the week ;-)) and you want to know all about packaging code so your users can install your library or application using the PEAR installer. A few things first:<br />
<br />
1. You don't need to propose a package to PEAR to do this.<br />
2. You don't need to create a PEAR "channel" although it's very much recommended (another future blog post no doubt).<br />
3. You don't need a whole lot of effort.<br />
<br />
Taking your source code, and generating a PEAR package is a relatively simple task.</blockquote>

He covers <a href="http://blog.astrumfutura.com/archives/312-Doing-that-thing-called-PEAR-Packaging-Source-Code-for-PEAR-Distribution.html">the process</a> at lengths with easy to follow steps.]]></description>
      <pubDate>Fri, 26 Oct 2007 14:56:51 -0500</pubDate>
    </item>
  </channel>
</rss>
