Has the [install_path] attribute been deprecated?

Lines 134-136 of drush_make.utilities.inc seem to suggest it has. What is the new method for a makefile to be able to specify where the project files will be put please?

Specifying --contrib-destination on the stub makefile that downloads the profile (with the makefile in it) doesn't seem to persist, so the projects default to profiles/profilename/modules still.

Other install profiles such as Open Publish also rely on [install_path]

Thanks for any help - and thanks for drush_make, it's awesome :)

Comments

dmitrig01’s picture

dmitrig01 commented

Depends what you want to do. Do you mean you want projects in sites/all? Semantically, profile-related projects should be in profile/profilename. Why would you want it another way?

steveparks’s picture

steveparks commented

Yes, we used the option of putting all projects in sites/all before.

It's not a big deal, but we like having one place where contrib modules/themes are stored to avoid someone uploading the same module to sites/all and causing a namespace issue.

We also then only give devs access to the symlinked sites/ directory to upload modules, updates etc, and only those directories are versioned.

As I say, not a big problem, but [install_path] just suddenly stopped working and I wondered if there was an important reason for removing the option to override the default location, and if a new way to override this was going to be introduced.

steveparks’s picture

steveparks commented

One issue with this being deprecated turns out to be when including external libraries in a makefile. You lose the ability to place them in sites/all/libraries which is where many modules require them to be (eg WYSIWYG module and the TinyMCE, FCKEditor etc libraries)

pcambra’s picture

pcambra
he/him
Primary language Spanish
commented

suscribe

yhahn’s picture

yhahn commented
Status: Active » Closed (works as designed)

  1. The install_path option is indeed deprecated. --contrib-destination is the proper flag to use when choosing a different root directory for projects.

  2. As of now, having an install profile makefile write to directories higher than its designated directory is not supported. FYI, the Libraries module does support libraries in profiles/[profile]/libraries.