according to docs:

The modules will be installed into a site specific modules directory if one
exists, otherwise sites/all/modules is used.
After installing, you still have to activate on the normal module
administration page

Would be good to be able to force drush to install into sites/all/modules

Comments

vingborg’s picture

vingborg commented

It would be even better if the install directory could be specified explicitly, so, for instance, the packages would go into a 'contrib' folder beneath the site specific modules folder or something like that.

mlncn’s picture

mlncn commented
Assigned: Unassigned » mlncn
Status: Active » Postponed

My thoughts exactly.

I think this feature should wait for Drush does not have to be a module to shake down, but then I'd like to work on it.

Should a flag to set the install path to anywhere be defined in the drush command flags (drush [options] pm install/update etc.) or should a new place to define flags after the pm be created for the package manager module (drush pm [options] install/update etc.)?

benjamin, Agaric Design Collective

owen barton’s picture

owen barton commented
Status: Postponed » Closed (fixed)

You can now do this with drush dl --destination=whatever