3 ; This is an example makefile to introduce new users of drush_make to the
4 ; syntax and options available to drush_make. For a full description of all
5 ; options available, see README.txt.
7 ; This make file is a working makefile - try it! Any line starting with a `;`
12 ; Each makefile should begin by declaring the core version of Drupal that all
13 ; projects should be compatible with.
19 ; Every makefile needs to declare it's Drush Make API version. This version of
20 ; drush make uses API version `2`.
26 ; In order for your makefile to generate a full Drupal site, you must include
27 ; a core project. This is usually Drupal core, but you can also specify
28 ; alternative core projects like Pressflow. Note that makefiles included with
29 ; install profiles *should not* include a core project.
31 ; Use Pressflow instead of Drupal core:
32 ; projects[pressflow][type] = "core"
33 ; projects[pressflow][download][type] = "file"
34 ; projects[pressflow][download][url] = "http://launchpad.net/pressflow/6.x/6.15.73/+download/pressflow-6.15.73.tar.gz"
36 ; Git clone of Drupal 7.x. Requires the `core` property to be set to 7.x.
37 ; projects[drupal][type] = "core"
38 ; projects[drupal][download][type] = git
39 ; projects[drupal][download][url] = http://git.drupal.org/project/drupal.git
45 ; Each project that you would like to include in the makefile should be
46 ; declared under the `projects` key. The simplest declaration of a project
49 ; To include the most recent views module:
53 ; This will, by default, retrieve the latest recommended version of the project
54 ; using its update XML feed on Drupal.org. If any of those defaults are not
55 ; desirable for a project, you will want to use the keyed syntax combined with
58 ; If you want to retrieve a specific version of a project:
60 ; projects[views] = 2.16
62 ; Or an alternative, extended syntax:
64 projects[ctools][version] = 1.3
66 ; Check out the latest version of a project from Git. Note that when using a
67 ; repository as your project source, you must explicitly declare the project
68 ; type so that drush_make knows where to put your project.
70 projects[data][type] = module
71 projects[data][download][type] = git
72 projects[data][download][url] = http://git.drupal.org/project/views.git
73 projects[data][download][revision] = DRUPAL-6--3
75 ; For projects on drupal.org, some shorthand is available. If any
76 ; download parameters are specified, but not type, the default is git.
77 projects[cck_signup][download][revision] = "2fe932c"
78 ; It is recommended to also specify the corresponding branch so that
79 ; the .info file rewriting can obtain a version string that works with
80 ; the core update module
81 projects[cck_signup][download][branch] = "7.x-1.x"
83 ; Clone a project from github.
85 projects[tao][type] = theme
86 projects[tao][download][type] = git
87 projects[tao][download][url] = git://github.com/developmentseed/tao.git
89 ; If you want to install a module into a sub-directory, you can use the
92 projects[admin_menu][subdir] = custom
94 ; To apply a patch to a project, use the `patch` attribute and pass in the URL
97 projects[admin_menu][patch][687750] = "http://drupal.org/files/issues/admin_menu.long_.31.patch"
99 ; If all projects or libraries share common attributes, the `defaults`
100 ; array can be used to specify these globally, rather than
103 defaults[projects][subdir] = "contrib"