Drush 5 and provision 6.x-2.x

So Provision-6.x-2.x should be available in the aegir-dev blueprint, by setting some variables in the hm.pp manifest. If 2.x requires Drush5, then this won't work anymore. Either way, I need to refactor the Drush Puppet module, similarly to how I did for the Aegir Puppet module, to allow us to specify a 'manual' install from Git repos, with proper handling of branches, &c.

By the way, I'll be putting out a new release of Aegir-up in the next week or two, that uses new Drush Vagrant 2.x functionality.

I merged the update_aegir branch into 7.x-2.x. I'd also done the re-factoring in puppet-drush to allow installing Drush from source. All this is in the 'aegir-dev' blueprint.

I'm marking as needs review, as the testing against both the stable stack (drush-vagrant 2.x & drush-hosts 1.x), and the latest dev (drush-vagrant 3.x, drush-hosts 2.x) would be greatly appreciated. Following that, and an update to the base-boxes, I think stable releases across the board would be in order.

using drush-vagrant 3.x and drush hosts 1.x (i cannot find 2.x) with aegir-up 2.x-dev aegir-dev actually installs! only thing is - i cannot seem to find the aegir folder (with the platforms) on my host. should NFS be working a documented? where should those files be? EDIT: Found the relevant setting in /.drush/aegir-up/blueprints/aegir-dev/settings.rb

Please update the documented installation instructions. This had me confused as heck before I realized the module now relies completely on drush_vagrant, especially considering aegirup.drush.inc still contains [incomplete] drush hook implementations and there's no mentioning of it elsewhere.

The docs themselves had been updated, but the links from the project page were out of date. Thanks for pointing that out.

Ah, that explains it, thanks.