Is there a clear plan on merging drush_mm and drush ?
rsvelko - May 14, 2009 - 15:23
| Project: | Drush Module Manager |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hi, since I just want to list my modules the drush_mm way and drush is currently not satisfying me - what would be the right way to make drush more drush_mm-ish ?
@clemens: Have you thought of the possible scenarios?
#1
drush_mm is good on it's own.
What I hope to find time for is to convince drush to support an eco system of supporting modules. See ie http://drupal.org/project/drush_sm which is another drush extension.
But I agree with your listing favours. With drush_mm you can almost get the list and input it into another drupal install enabling the modules.
#2
the situation is as follows now - drush_mm works fine with the current drush and I use it .
Drupal modules provide their own commands and drush_mm too. Drush maintainers do not need to be convinced - they've made drush extension friendly - so you go on and develop your commands in drush_mm and sm.
PS. See context/spaces/patterns modules's efforts - they do similar things to your drush_sm. They have drush commands too.
#3
drush core has all of these commands now: enable, disable, uninstall and perhaps others
Are they different in any way? Perhaps if they are better, the improvements should be moved into drush core, and drush_mm should focus on it's other features?
#4
drush lacks two features now:
- enabling/dl-ing required modules - I believe drush_mm does the enable part of that
- nice one-line module listing - drush_mm's "mm list" command that is feedable to enable...
as for the enable/disable/dl/uninstall part - drush core is ok (as well as drush_mm)
up to you.