How to use the latest version of Pressflow Drupal with Drush Make

Tech Blog :: How to use the latest version of Pressflow Drupal with Drush Make

Jun 21 '10 10:50am

Link
Shrt.ct

Pressflow is a performance-tuned, MySql-specific distribution of Drupal maintained by Four Kitchens. Drush Make is a way of automatically compiling the files needed to build a big Drupal site.

I posted this issue on Pressflow's Launchpad queue (after raising the question with their team at D4D):

I'm using Drush Make to build my sites and I'd like Pressflow to be the default core. It's easy to put projects[] = drupal in the make file and it gets the latest 6.x from drupal.org. But how do I get the latest Pressflow? Currently I have:
projects[drupal][download][url] = "http://launchpad.net/pressflow/6.x/6.16.77/+download/pressflow-6.16.77.tar.gz"
projects[drupal][download][type] = "get"
For every Pressflow upgrade, I have to change the path there manually, which mostly defeats the purpose of Drush Make (and is a barrier to using Pressflow). It would be great if I could simply put in http://launchpad.net/pressflow/6.x/6.x-latest.tar.gz and it would always fetch the latest version. Or better yet, have projects[] = pressflow instead of "drupal," but I don't want to press my luck...

Thank you!

David Strauss (creator of Pressflow) replied:

Two options:

* Use Drush Make's support for Bazaar, and use lp:pressflow
* Use this URL to our build server: http://files.pressflow.org/pressflow-6-current.tar.gz

Nice!

By EclipseGc (not verified) on Mon, 06/21/2010 - 15:03:

I may misunderstand exactly how pressflow is being put together to begin with, but it would be much nicer if we could just point at a repository that contained another make file that 4 kitchens kept up-to-date with references to the currently used patches so that we could pull vanilla drupal and apply the various patches that make it pressflow, instead of having to wait for the 4 kitchens guys to have to manually release a new version of pressflow to match the newest version of drupal core.

By dalin (not verified) on Mon, 06/21/2010 - 23:23:

The patch-set would be huge and difficult to maintain. There is a lag between a Drupal release and the corresponding Pressflow release because there needs to be testing done to ensure that the latest Drupal changes don't break something in Pressflow or vice-verse.

By but there are conflicting patchsets (not verified) on Tue, 06/22/2010 - 10:04:

Unfortunately that's not possible because the patches between vanilla Drupal and Pressflow don't always apply when there is a new version of core. Drupal 6.17 for example had a bunch of changes that broke the patches and required manual merging of the codebases.

There may be times when the patch philosophy works (e.g. perhaps 6.18 will be small enough of a change), but in general it's not possible.

Fortunately David is quite quick at rolling new releases.

By Sean Bannister (not verified) on Tue, 06/22/2010 - 01:21:

Thanks Ben, was thinking about this last week.

One thing I noticed in lullabot's "Drush Make and Pressflow" article is they also include:
projects[pressflow][type] = "core"

Haven't had a chance to look at the docs but I presume if lullabots doing it, hopefully they looked into it ;)

- Sean Bannister

By ben on Tue, 06/22/2010 - 13:26:

Interesting. I was using projects[drupal] which I guess Drush Make assumes is type="core", they were using projects[pressflow] so (I presume) they had to specify. I wonder if it makes a difference, good to know though.