search

xforty / drush-deploy

Drupal deploy tool based on Capistrano and Drush
https://github.com/xforty/drush-deploy/wiki
Other
35 stars 4 forks source link

Support d.o. standard naming conventions for install profile packaging #24

Open dkingofpa opened 11 years ago

dkingofpa commented 11 years ago

Managing drush make files for an installation profile

As @patcon mentioned in xforty/drush-deploy#23, we should start supporting the d.o. naming convention by default. I'm looking to do this with xforty/xforty-drupal7#5.

I believe we currently just look for a distro.make file. We could first look for a build-.make file to support the new naming convention. If that isn't found, we can then look for a distro.make for backwards compatibility.

patcon commented 11 years ago

Ah cool! And for build-[distro].make, if the tool also had the option to edit stdin on the fly before passing it to drush, would be nice to have a flag to build a certain git reference.

So it would find this line if it exists:

projects[myprofile][download][revision] = whatever

and replace "whatever" with any git ref that's passed in.

This allows for the build/deploy of any git commit from the history. Otherwise, the official d.o profile format is a little limited in that it can only easily build whatever happens to be hardcoded into build-[distro].make.

Cheers! Thanks for creating the issue! If it makes more sense, perhaps #5 could be the simple change, and this could be for the on-the-fly revision insertion?

EDIT: Just realized that was xforty/xforty-drupal7#5, so scratch that suggestion. Let me know if the above feature makes sense, and if so, whether you'd rather it be a new issue.