Build Managing News for Development

On this page

1. Getting working copies
2. Rebuilding Managing News
3. Packaging Managing News
4. Upgrading to the next release of Managing News
5. See also

Managing News uses an install profile and a Drush make based build system. Complete and ready to install downloads are offered at http://managingnews.com, but it's also possible to build Managing News yourself. You may want to do this to participate in Managing News development, or to simply check out the bleeding edge.

Developers, or other users, who wish to build Managing News themselves will need to have Drush, Drush make and Git installed. It's highly recommended to use the most recent version of Drush, version 3.x.

To emulate how drupal.org builds profiles into full Drupal installs you need to use a stub makefile;

core = "6.x"
projects[] = "drupal"
projects[managingnews][type] = "profile"
projects[managingnews][download][type] = "git"
projects[managingnews][download][url] = "git://git.drupal.org/project/managingnews.git"
projects[managingnews][download][branch] = "6.x-1.x"

Paste this code into a file called managingnews_stub.make and run:

drush make managingnews_stub.make managingnews

This will assemble a full Managing News build into the directory managingnews.

Getting working copies

A make file can specify that a project is retrieved in two main ways; a direct download, or from a version control system. If the make file specifies that some projects should be retrieved from a version control system, by default the code will be exported, not checked out. In order to have Drush check out the code and you can use the --working-copy flag. Like:

drush make --working-copy managingnews_stub.make managingnews

Rebuilding Managing News

As changes are committed to various repositories, and new releases made available it can be useful to completely rebuild the contents of profiles/managingnews/modules and profiles/managingnews/themes. To make this simple there is a shell script included in the Managing News profile that uses Drush make to re-fetch all the components of the install profile.

To use this drush must be in your $PATH and you'll want to remove the modules and themes directories completely. Be sure you don't have any customizations there that you want to keep, and it's probably worth making a backup anyhow. You may need to make rebuild.sh executable, if you do simply run chmod a+x rebuild.sh.

For example to rebuild your Managing News install profile you would:

cd ./profiles/managingnews
tar -czf backup.tar.gz modules/ themes/ translations/
rm -rf ./modules/ ./themes/ ./translations/
./rebuild.sh

When prompted, select Rebuild Managing News in place. and then confirm that you want to "Make new site in the current directory?"

Note: it's possible, though highly unlikely, that your webserver is configured to run shell scripts. If you suspect this is the case you'll want to remove rebuild.sh.

Packaging Managing News

The rebuild.sh script can also be used to package a full distribution (Drupal + the Managing News install profile). To do this you'll need have a git checkout of Managing News. Run rebuild.sh and select Build a full Managing News distribution. The script will save a full Managing News package as a .tar.gz file with a name based on what branch of the project you have checked out. For example managingnews-head.tar.gz or managingnews-1-0-beta7.tar.gz.

Upgrading to the next release of Managing News

Once you are running beta4 or later (all Managing News files are in /profiles/managingnews), upgrading to beta6, beta7, etc. is a matter of getting the latest managingnews.make from git, getting the latest managingnews.profile, then running rebuild.sh.

See also

External resources

• Managing News
• Managing News - drupal.org
• Drush Make - drupal.org
• Drush - drupal.org