Option for pm-enable to enable disabled dependencies

how does drupal core handle newly added dependencies? this is sort of tricky.

As a workaround, how about drush dis modulename && drush en modulename?

None of those consequences should entail data loss (thats what uninstall is for) - but I agree. Not a wise path.

How about we enhance pm-enable such that it works for already enabled extensions. Namely, it actually calls module_enable() and thus any new dependencies as enabled. would work on D7 at least.

That's one small step for a man, ...

example:

$ drush en email
The following extensions will be enabled: email
Do you really want to continue? (y/n): y
email was enabled successfully.                                                                                                                   [ok]

$ echo "dependencies[]=text" >> modules/email/email.info 

$ drush en email
email is already enabled.                                                                                                                         [ok]
The following extensions will be enabled: text
Do you really want to continue? (y/n): y

polished

Well done.

Committed. Perhaps Mark wants this in 4.x

I really like this patch, but I'm on the fence about whether this is safe to backport because it does change behavior.

I could use a second opinion on this if anyone else has a different take.

I think it is okay to backport; it extends old behavior, should not break any existing scripts or code.

k, backported.