1
|
; $Id: EXAMPLE.make,v 1.1.2.4 2010/09/04 16:11:37 dmitrig01 Exp $
|
2
|
;
|
3
|
; Example makefile
|
4
|
; ----------------
|
5
|
; This is an example makefile to introduce new users of drush_make to the
|
6
|
; syntax and options available to drush_make. For a full description of all
|
7
|
; options available, see README.txt.
|
8
|
|
9
|
; This make file is a working makefile - try it! Any line starting with a `;`
|
10
|
; is a comment.
|
11
|
|
12
|
; Core version
|
13
|
; ------------
|
14
|
; Each makefile should begin by declaring the core version of Drupal that all
|
15
|
; projects should be compatible with.
|
16
|
|
17
|
core = 6.x
|
18
|
|
19
|
; Core project
|
20
|
; ------------
|
21
|
; In order for your makefile to generate a full Drupal site, you must include
|
22
|
; a core project. This is usually Drupal core, but you can also specify
|
23
|
; alternative core projects like Pressflow. Note that makefiles included with
|
24
|
; install profiles *should not* include a core project.
|
25
|
|
26
|
; Use pressflow instead of Drupal core:
|
27
|
; projects[pressflow][type] = "core"
|
28
|
; projects[pressflow][download][type] = "get"
|
29
|
; projects[pressflow][download][url] = "http://launchpad.net/pressflow/6.x/6.15.73/+download/pressflow-6.15.73.tar.gz"
|
30
|
|
31
|
; CVS checkout of Drupal 6.x core:
|
32
|
; projects[drupal][type] = "core"
|
33
|
; projects[drupal][download][type] = "cvs"
|
34
|
; projects[drupal][download][root] = ":pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal"
|
35
|
; projects[drupal][download][revision] = "DRUPAL-6"
|
36
|
; projects[drupal][download][module] = "drupal"
|
37
|
|
38
|
; CVS checkout of Drupal 7.x. Requires the `core` property to be set to 7.x.
|
39
|
; projects[drupal][type] = "core"
|
40
|
; projects[drupal][download][type] = "cvs"
|
41
|
; projects[drupal][download][root] = ":pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal"
|
42
|
; projects[drupal][download][revision] = "HEAD"
|
43
|
; projects[drupal][download][module] = "drupal"
|
44
|
|
45
|
projects[] = drupal
|
46
|
|
47
|
; Projects
|
48
|
; --------
|
49
|
; Each project that you would like to include in the makefile should be
|
50
|
; declared under the `projects` key. The simplest declaration of a project
|
51
|
; looks like this:
|
52
|
|
53
|
projects[] = views
|
54
|
|
55
|
; This will, by default, retrieve the latest recommended version of the project
|
56
|
; using its update XML feed on Drupal.org. If any of those defaults are not
|
57
|
; desirable for a project, you will want to use the keyed syntax combined with
|
58
|
; some options.
|
59
|
|
60
|
; If you want to retrieve a specific version of a project:
|
61
|
|
62
|
projects[cck] = 2.6
|
63
|
|
64
|
; Or an alternative, extended syntax:
|
65
|
|
66
|
projects[ctools][version] = 1.3
|
67
|
|
68
|
; Check out the latest version of a project from CVS. Note that when using a
|
69
|
; repository as your project source, you must explictly declare the project
|
70
|
; type so that drush_make knows where to put your project.
|
71
|
|
72
|
projects[data][type] = module
|
73
|
projects[data][download][type] = cvs
|
74
|
projects[data][download][module] = contributions/modules/data
|
75
|
projects[data][download][revision] = DRUPAL-6--1
|
76
|
|
77
|
; Clone a project from github.
|
78
|
|
79
|
projects[tao][type] = theme
|
80
|
projects[tao][download][type] = git
|
81
|
projects[tao][download][url] = git://github.com/developmentseed/tao.git
|
82
|
|
83
|
; If you want to install a module into a sub-directory, you can use the
|
84
|
; `subdir` attribute.
|
85
|
|
86
|
projects[admin_menu][subdir] = custom
|