This patch, written by me and sponsored by A Mountain Top, adds the ability for Drush to enable and disable modules in Drupal. It has been tested by me using various modules, and various dependency scenarios, and comes through like a trooper each time.

Robin

CommentFileSizeAuthor
#1 1195745.patch7.59 KBrobin monks

Comments

robin monks’s picture

robin monks commented
StatusFileSize
new 1195745.patch7.59 KB

Gah, patch didn't attach...

moshe weitzman’s picture

moshe weitzman commented

I've been torn on this for a long time. I hate copying so much dependancy code from core. Any chance you can submit a patch for D7 to factor it out so we can avoid the code duplication. If your patch gets into 7, I'd feel better about putting this in D6. I don't really want to maintain this for a long time.

Any other opinions?

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented

He guys, this is already done in drush_mm. See #303861: Adding contrib drush modules and off course http://drupal.org/project/drush_mm

I like parts of the patches though. Clearing caches and actions.

I propose to add these to my project. What do you think?

Regards,

Clemens

robin monks’s picture

robin monks commented

clemens.tolboom, definitely, add this to your module.

That said, I would much rather see this go into coder itself, so, moshe: exactly what would you like to see for HEAD to make this happen?

Robin

moshe weitzman’s picture

moshe weitzman commented

Robin - I would like to see no code duplication between drush and core. That implies that core gets refactored so that we can just call its dependancy functions.

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented

XLinking #319501: Cleaning up when enabling and / or disabling.

@Robin : Please have a look over there :-)

moshe weitzman’s picture

moshe weitzman commented
Status: Needs review » Closed (duplicate)

#151561: expanding module installation