Moving from sites/all

Recently, we have been moving away from using sites/all to store modules and themes because we heavily use multisite setups and need to keep the sites contained and independent. To change a site away from using sites/all, I djinn'ed up a drush command that looks to see what's being invoked from sites/all. drush sql-query "select filename from system where status=1 and filename like 'sites/all%'" which will give a return delimited list of the filenames of modules that are enabled: sites/all/modules/cck/content.module sites/all/modules/cck/modules/text/text.module sites/all/modules/date/date/date.module sites/all/modules/date/date_api.module sites/all/modules/date/date_popup/date_popup.module sites/all/modules/date/date_timezone/date_timezone.module sites/all/modules/devel/devel_generate.module sites/all/modules/devel/devel.module sites/all/modules/admin_menu/admin_menu.module From this we can see that CCK, Date, Devel, and Admin Menu are the Drupal projects that need to be downloaded into the subsite directory. We really just need to get the arg(3) to know which projects to grab. I did this with awk and then changed the newlines to spaces to get a space delimited set of values to pass to drush dl drush sql-query "select filename from system where status=1 and filename like 'sites/all%'" | awk -F/ '{print $4}' | sort -u | tr '\n' ' ' This leaves us with the following: admin_menu cck date devel A nice space delimited set of projects to download. drush dl `drush sql-query "select filename from system where status=1 and filename like 'sites/all%'" | awk -F/ '{print $4}' | sort -u | tr '\n' ' '` which when run in the subsite directory (or with a site alias or uri parameter to drush) will get all of the projects necessary. Then simply running drush cc all seems to do the trick.