<?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>Thu, 20 Jun 2013 06:49:37 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Till Klampaeckel's Blog: Quo vadis PEAR?]]></title>
      <guid>http://www.phpdeveloper.org/news/13936</guid>
      <link>http://www.phpdeveloper.org/news/13936</link>
      <description><![CDATA[<p>
<i>Till Klampaeckel</i> has a recent post about <a href="http://till.klampaeckel.de/blog/archives/82-Quo-vadis-PEAR.html">PEAR versus PEAR Farm</a> on his blog detailing what each is and how to use the <a href="http://pearfarm.org/">PEAR Farm</a> to get your software out there.
</p>
<blockquote>
With the release of <a href="http://www.pirum-project.org/">Pirum</a>, I'm really excited to see two public PEAR channels that aim to make PEAR a standard to deploy and manage your applications and libraries. One is <a href="http://pearhub.org/">PEARhub</a> and the other is <a href="http://pearfarm.org/">PEAR Farm</a>. I think I'm gonna stick with PEAR Farm for a while, so this blog entry focuses on things I noticed when I first played with it. [...] A lot of people mistake these new channels for the wrong thing. They think that this will eventually replace PEAR. I don't think it will - ever.
</blockquote>
<p>
He shows how to get the PEAR Farm libraries installed (via the PEAR installer) and how to set up your project with the pearfarm command-line tool. He also offers a few "gotchas" and tips to help you with a few of the issues he saw along the way. You can get an idea of the end result by looking at <a href="http://pearfarm.org/till">Till's PEAR Farm page</a>.
</p>]]></description>
      <pubDate>Fri, 29 Jan 2010 11:24:46 -0600</pubDate>
    </item>
  </channel>
</rss>
