Right now running drush -y make --contrib-destination=profiles/myprofile/modules/contrib profiles/myprofile/myprofile.make adds the folder modules in profiles/myprofile/modules/contrib. It would be nice if when defining --contrib-destination the folder modules isn't added.

Makes the folder setup cleaner :)

Comments

helmo’s picture

Title: --contrib-destination add folder modules » --contrib-destination adds folder like modules or themes
Project: Drush Make » Drush
Version: 6.x-3.x-dev »
Component: Code » Make

[ 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 queue has a component 'Make' especially for drush_make.

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

NOTE:
Problem is that contrib-destination is also used for themes, then 'themes' is appended.

To fix this the option would have to be split, or defined per project.

helmo’s picture

steven jones’s picture

If you're trying to 'remake' your profile, then the easiest way is to cd into the profile's directory and pass in the option: --contrib-destination=.

kenorb’s picture

Version: » 7.x-5.x-dev

The same problem with drush 5.8
I've specified sites/all/modules/contrib, but it's downloading into sites/all/modules/contrib/modules

steven jones’s picture

@kenorb Try specifying the --contrib destination as 'sites/all' and then using the 'subdir' element in the make file of each project to get the module/theme into the 'contrib' subdirectory with modules/themes? Does that work for you?

greg.1.anderson’s picture

Version: 7.x-5.x-dev » 8.x-6.x-dev
Status: Active » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.