<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>drush on Dave Hall (@skwashd)</title><link>https://www.skwashd.net/tags/drush/</link><description>Recent content in drush on Dave Hall (@skwashd)</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 17 May 2011 00:00:00 +0000</lastBuildDate><atom:link href="https://www.skwashd.net/tags/drush/index.xml" rel="self" type="application/rss+xml"/><item><title>Drush Make and Module Dependencies</title><link>https://www.skwashd.net/posts/2011-05-17-drush-make-and-module-dependencies/</link><pubDate>Tue, 17 May 2011 00:00:00 +0000</pubDate><guid>https://www.skwashd.net/posts/2011-05-17-drush-make-and-module-dependencies/</guid><description>Drush make is a wonderful tool for constructing Drupal platforms. A lot of Drupal developers are used to adding a list of modules, a few libraries and theme or 2 then running drush make to build their platform.</description></item><item><title>Packaging Drush and Dependencies for Debian</title><link>https://www.skwashd.net/posts/2010-02-04-packaging-drush-and-dependencies-debian/</link><pubDate>Thu, 04 Feb 2010 00:00:00 +0000</pubDate><guid>https://www.skwashd.net/posts/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.</description></item></channel></rss>