Could you elaborate on why this is useful, and what it would do? pm-download already recognizes when projects only include drush commands and puts those in ~/.drush where they can actually be used. Not sure how related that is.
Hm. Maybe I'm missing a piece. How else would we get a drush extension into sites/all/profiles/drush, should we wanted to store it in the app-specific location (assuming we're building a project as an install profile and want total control over a self-contained project with known versions of all tools, including drush extensions).
I suppose I was thinking that any item that had a specific folder (modules/themes/profiles) deserved its own type?
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).
The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.
Comments
Comment #1
moshe weitzman commentedCould you elaborate on why this is useful, and what it would do? pm-download already recognizes when projects only include drush commands and puts those in ~/.drush where they can actually be used. Not sure how related that is.
Comment #2
patcon commentedHm. Maybe I'm missing a piece. How else would we get a drush extension into
sites/all/profiles/drush, should we wanted to store it in the app-specific location (assuming we're building a project as an install profile and want total control over a self-contained project with known versions of all tools, including drush extensions).I suppose I was thinking that any item that had a specific folder (modules/themes/profiles) deserved its own type?
Comment #3
jonhattanThe types we recognize are the ones declared by drupal.org and exposed in the update service. See #322626: META: Package and version non-modules for download.
Comment #4
greg.1.anderson commentedThis 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.