What Drupal Needs: Drush with Dependencies

Drupal needs smarter packaging scripts.

If you get a module that depends on another module, they should both be delivered to you (and so forth).

But to do this Drupal needs to know what's on your system, so you have to be initiating the transfer from within Drupal. Drush could do this fairly securely.

We need to encourage the lots of small modules approach that everyone loves from the development and extensibility side, but which the difficulty of developing, maintaining, and using can drag down.

Modules maintained by different people suffer from not being able to effortlessly include the work of the other.

The current solution is to throw more modules into one project. This may be a good solution. It does require project leaders to be generous with CVS commit access, and it hasn't happened enough.

Resolution