<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pear on Dave Hall Consulting</title><link>https://www.davehall.com.au/tags/pear/</link><description>Recent content in Pear on Dave Hall Consulting</description><generator>Hugo</generator><language>en-au</language><lastBuildDate>Mon, 12 Oct 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://www.davehall.com.au/tags/pear/index.xml" rel="self" type="application/rss+xml"/><item><title>Packaging Drush and Dependencies for Debian</title><link>https://www.davehall.com.au/blog/2010/02/04/packaging-drush-and-dependencies-debian/</link><pubDate>Thu, 04 Feb 2010 00:00:00 +0000</pubDate><guid>https://www.davehall.com.au/blog/2010/02/04/packaging-drush-and-dependencies-debian/</guid><description>Lately I have been trying to avoid non packaged software being installed on production servers. The main reason for this is to make it easier to apply updates. It also makes it easier to deploy new servers with meta packages when everything is pre packaged.
One tool which I am using a lot on production servers is Drupal&amp;rsquo;s command line tool - drush. Drush is awesome it makes managing Drupal sites so much easier, especially when it comes to applying updates.</description></item></channel></rss>