3 # This is an example makefile to introduce new users of drush make to the
4 # syntax and options available to drush make.
6 # This make file is a working makefile - try it! Any line starting with a `#`
11 # Each makefile should begin by declaring the core version of Drupal that all
12 # projects should be compatible with.
18 # Every makefile needs to declare it's Drush Make API version. This version of
19 # drush make uses API version `2`.
25 # In order for your makefile to generate a full Drupal site, you must include
26 # a core project. This is usually Drupal core, but you can also specify
27 # alternative core projects like Pressflow. Note that makefiles included with
28 # install profiles *should not* include a core project.
30 # Use Pressflow instead of Drupal core:
36 # url: "http://launchpad.net/pressflow/6.x/6.15.73/+download/pressflow-6.15.73.tar.gz"
38 # Git clone of Drupal 7.x. Requires the `core` property to be set to 7.x.
43 # url: "http://git.drupal.org/project/drupal.git"
51 # Each project that you would like to include in the makefile should be
52 # declared under the `projects` key. The simplest declaration of a project
55 # To include the most recent views module:
60 # This will, by default, retrieve the latest recommended version of the
61 # project using its update XML feed on Drupal.org. If any of those defaults
62 # are not desirable for a project, you will want to use the keyed syntax
63 # combined with some options.
65 # If you want to retrieve a specific version of a project:
70 # Or an alternative, extended syntax:
75 # Check out the latest version of a project from Git. Note that when using a
76 # repository as your project source, you must explicitly declare the project
77 # type so that drush_make knows where to put your project.
82 type: "git" # Note, 'git' is the default, no need to specify.
83 url: "http://git.drupal.org/project/views.git"
86 # For projects on drupal.org, some shorthand is available. If any
87 # download parameters are specified, but not type, the default is git.
91 # It is recommended to also specify the corresponding branch so that
92 # the .info file rewriting can obtain a version string that works with
93 # the core update module
96 # Clone a project from github.
101 url: "git://github.com/developmentseed/tao.git"
103 # If you want to install a module into a sub-directory, you can use the
104 # `subdir` attribute.
109 # To apply patches to a project, use the `patch` attribute and pass in the URL
110 # of the patch, one per line prefaced with `- `.
113 - "http://drupal.org/files/issues/admin_menu.long_.31.patch"
115 # If all projects or libraries share common attributes, the `defaults`
116 # array can be used to specify these globally, rather than