It would be great to get some documentation on how module maintainers should be using .make files in their modules in order to automate the downloading of dependent libraries.

For example, we have having trouble over at the geofield module getting a module-level make file to work correctly. The issue is here: http://drupal.org/node/1122024

Comments

mrfelton’s picture

mrfelton commented

the salesforce module has the same problem. I think that the general chain of though at the moment is that the makefile should be called modulename.make.example so that it doesn't run automatically, since this breaks distribution builds.

attiks’s picture

attiks commented
Category: task » feature

The problem occurs if your make file includes the same line as the included one does, make drush make can detect this and not download a project once it's already downloaded?

attiks’s picture

attiks commented
Status: Active » Closed (duplicate)

this is/will be fixed: #947158: Recursive makefiles can cause conflicts