Closed (won't fix)
Project:
Drush
Version:
8.x-6.x-dev
Component:
Make
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Nov 2012 at 14:27 UTC
Updated:
11 Sep 2013 at 05:18 UTC
I'd like to create a make-file that drops modules and themes into a subfolder of /profiles in order to replace existing modules and themes, and add new ones.
Given a make file along these lines:
projects[advanced_help][subdir] = sites/all/modules/contrib
projects[advanced_help][version] = 1.2
projects[boxes][subdir] = profiles/myprofile/modules/contrib
projects[boxes][version] = 1.1
projects[tao][version] = 3.3
projects[tao][subdir] = profiles/myprofile/themes
libraries[jquery_ui][download][type] = get
libraries[jquery_ui][download][url] = http://jquery-ui.googlecode.com/files/jquery-ui-1.7.3.zip
libraries[jquery_ui][directory_name] = jquery.ui
libraries[jquery_ui][destination] = profiles/myprofile/modules/contrib/jquery_ui
; CKEditor
libraries[ckeditor][download][type]= get
libraries[ckeditor][download][url] = http://download.cksource.com/CKEditor/CKEditor/CKEditor%203.6.5/ckeditor_3.6.5.tar.gz
libraries[ckeditor][directory_name] = ckeditor
libraries[ckeditor][destination] = sites/all/libraries
and a command like this:
cd drupal-root; drush make --no-core --contrib-destination=. mymakefile.make
- this results in only the libraries going where I want them.
The modules and theme end up in /modules/sites/.. and /modules/profiles/... ie. the core modules folder. The theme ends up in /themes/profiles/myprofile/themes/tao :-(
I would expect there to be no restrictions or magic happening when supplying --contrib-destination=. from the Drupal root folder.
Comments
Comment #1
achtonAh, it seems there was a similar issue filed against Drush Make: #1337468: --contrib-destination adds folder like modules or themes
Comment #2
greg.1.anderson commentedThis issue was marked
closed (won't fix)because Drush has moved to Github.If desired, you may copy this bug to our Github project and then post a link here to the new issue. Please also change the status of this issue to
closed (duplicate).Please ask support questions on Drupal Answers.