We are experimenting with Features and Drush Make looked promising to close the gap to make Features a one click install (or close to it).

The scenerio is that we have a Feature that depends on apachesolr and has some custom code for our needs. The Feature right now needs some help which since the steps to install are

  1. Get Feature and untar/zip
  2. Drush dl get apachesolr
  3. Look up INSTALL.txt and get the svn location of external library (SolrPhpClient)
  4. Enable Feature

Which is not very different than just getting our module and doing the rest of the steps. I am hoping to include a .make file that Drush Make could provide some shortcuts to get the dependencies of a feature, including external dependencies (which I saw was possible from another ticket).

I am having trouble getting this to work. I got around not downloading core with --no-core, but am having problems figuring a good way to download modules to the usual place (sites/all/modules). The behavior I am seeing is that it 

cd /home/jskulski/public_html/jskulski/sites/all/modules php /usr/local/drush/drush.php -l http://jskulski.chapterthree.com -r /home/jskulski/public_html/jskulski make --debug --no-core --contrib-destinations=wut /home/jskulski/public_html/jskulski/sites/all/modules/chapter3_search/chapter3_search.make

does not seem to respect the contrib-destination argument and nests a sites/all/modules within sites/all/modules (yo dawg). I tried other contrib-destinations likes "" "/" to try to get it to use the sites/all/modules, but it still nested or told me that the directory already existed (but I did not save that director)

Is there a way to get drush make to simulate the behavior of `drush dl` which just adds it to an existing project instead of expecting a project to be create? Could this behavior be wrapped into a --no-core setting and relocated into the .make file?

Thanks, great module.

Comments

dmitrig01’s picture

dmitrig01 commented

Yep. This, however, would be something for 3.x. Ideally what I'd want to do in 3.x is have drush first map out all the projects in a site, including both existing ones and ones to be downloaded, and then download the ones to be downloaded.

The cool thing about this model would be that drush dl could then use the drush_make infrastructure, and drush updatecode would be a piece of cake as well.

Grayside’s picture

Grayside commented

subscribe

dmitrig01’s picture

dmitrig01 commented
Status: Active » Postponed
geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented

subscribe...!

dmitrig01’s picture

dmitrig01 commented
Title: Simulating `drush dl` with drush » Simulating `drush dl` with drush make
Status: Postponed » Active

I think this is now technically feasible

dmitrig01’s picture

dmitrig01 commented
Status: Active » Postponed

... but will not happen anytime soon

cosmicdreams’s picture

cosmicdreams commented

Ah here's the issue I've been running into.

i was hoping I could simulate a full drush_make build of my drupal site in order to debug why I was getting an error prevented downloaded site to be copied to my designated folder.

Following to see if anything can be done to fix this.

helmo’s picture

helmo commented
Status: Postponed » Closed (won't fix)

[ Powered by #1115636: Issue Macros and Templates - Drush Make]

Drush make is being merged into drush core (discussed in issue:#1310130: Put drush make in drush core)
This means that the issue queue is also moving. The Drush project has a component called 'Make' for this purpose.

We would like to take this opportunity to leave behind old/obsolete issues, allowing us to focus on a stable make command in core. E.g. one of the major tasks ahead is making more use of the Drush core code for handling downloads and decompression.

If you feel that this issue is still relevant, feel free to re-open and move it to the Drush queue.

More information will be posted on the drush_make and drush project pages.