Drupal Answers is a question and answer site for Drupal developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've created a project that is basically a drush command with a starterkit folder. I noticed the make_local project will but I haven't figured out how it does that.

I've tried the approach recommended in the answers and added a .info file and tried to hide the .profile extension by renaming it to .profile.starterkit. Drush still thinks I'm downloading a theme.

share|improve this question
up vote 4 down vote accepted

There are three requirements:

  1. Your project must have a .info file
  2. Your project must have a project.drush.inc file
  3. Your project must not have a project.module file or any sort of .profile file

If all three of these are true, then Drush will store the project in ~/.drush. If there is a module file or a .profile, then Drush will treat the project like a module or installation profile (usually storing it in sites/all/modules).

Your project was missing a .info file, but unfortunately, the existence of the profile file caused Drush to decide that your project was an installation profile, and Drush thinks that those do not belong in ~/.drush.

The user will have to specify --destination=$HOME/.drush, or move your project to the correct folder manually.

share|improve this answer
Thanks for the help greg! – Craig Jul 10 '14 at 14:45
I've added the .info file but that hasn't seemed to help. Here's what I see. drush dl panopoly_base_distribution_starter_kit Project panopoly_base_distribution_starter_kit (7.x-1.x-dev) downloaded to /home/drupalpro/projects/panopoly_base_distribution_starter_kit-7.x-1.x-dev. [success] Project panopoly_base_distribution_starter_kit contains: [success] - 1 profile: STARTERKIT - 1 theme: panopoly_base_distribution_starter_kit – Craig Jul 10 '14 at 19:30
Sorry, my answer was incomplete; I enhanced it. Previously, Drush did not think your project was a module (no .info file); now that there is an .info file, Drush thinks that your project is an installation profile. – greg_1_anderson Jul 10 '14 at 21:36
thanks! that is helpful. the .profile file is a starterkit file so I can always alter the extension and change when executing the drush command. – Craig Jul 10 '14 at 22:37
i'm getting closer. Drush no longer thinks I'm downloading a profile but still thinks I'm downloading a theme. – Craig Jul 11 '14 at 0:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.