Aegir3 can run on Drush 6, 7 or 8. However, we currently install Drush 6 in our Debian package. This makes using a more modern Drush more difficult. We could maintain .debs for drush6, drush7 and drush8, thus making it possible to run Aegir3 on any one of them.

Comments

ergonlogic created an issue. See original summary.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

We'll need to move to Drush 8 to support Drupal 8. These require PHP 5.6+, which could cause problems with Drupal 6 sites (contrib modules in particular). Giving ourselves the flexibility of continuing to host Drupal 6 sites, while also allowing Drupal 8 sites (even if not on the same server) seems warranted here.

helmo’s picture

helmo CreditAttribution: helmo as a volunteer and at Initfour websolutions commented

Some IRC discussion about this in our weekly chat: http://hefring.mig5.net/bot/log/aegir/2015-10-22#T595613

ac’s picture

ac
Primary language English
Location Perth
CreditAttribution: ac commented

Following this issue. From what I can tell Drush 8 requires PHP 5.4.5+ and Drupal 8 need 5.5.9+

gboudrias’s picture

gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commented
Related issues: +#2619158: Switch to Drush 8 by default
colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Colan Schwartz Consulting commented

Confirming #4 as per http://docs.drush.org/en/master/install/. So it looks like only Drush 8 is necessary now, but I still think there's value in a Drush Debian package.

So, as a compromise, how about providing one deb for now, just for Drush 8. The Aegir package can depend of any version though, if other Drush debs materialize.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic at Ergon Logic Enterprises for Aegir Cooperative commented

We have this: https://github.com/ergonlogic/drush.deb, which builds a usable Debian package for Drush. However, I'd be diffident to upload it to our debian repo and start depending on it. I think we'd need to have a proper maintenance plan in place for it.

A while back I started experimenting with OpenSuse's build service: https://build.opensuse.org/package/show/home:AegirProject/aegir3. I think that's likely the way to go here.

Ideally, we'd be able to commit a change bumping the Drush version number, and have TravisCI (or whatever) build packages, run tests, and upload the resulting .debs directly. Having a small reference implementation for a simple .phar deployment, like for Drush, would probably set the stage for moving in that direction for the rest of Aegir.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Colan Schwartz Consulting commented

Drush issue is https://github.com/drush-ops/drush/issues/2177.

helmo’s picture

helmo CreditAttribution: helmo as a volunteer and at Initfour websolutions commented

I've created a separate issue to be able to stop installing Drush from PHAR in the Debian post install

See: #2754309: Support installing Drush from deb package