What to do

The logical steps for creating a package definition file, typically named package.xml, that describes the dependencies required by your project are:

  1. List what you need - Include in this details such as what channels the packages are to be installed from and whether you only want very specific versions of those packages to be installed, or if you want to specify what the minimum versions of the packages should be.

  2. Create a package.xml including these packages as its manifest.

  3. Test that it works

Dependency Tracking (Meta Packages) with PEAR (Previous) Generating a list of what's needed (Next)
Last updated: Mon, 20 Oct 2014 — Download Documentation
Do you think that something on this page is wrong? Please file a bug report or add a note.
View this page in:

User Notes:

There are no user contributed notes for this page.