| Changes between PEAR REST interface versions (Previous) | (Next) Packages | ||||
| |
|||||
|
|||||
Use cases
This section shows common actions on a channel server and what to do then.
The idea and initial cases have been taken from Jean-Lou Dupont's "PEAR Channel on Google Code" presentation.
Adding a new category
When creating a fresh category on your channel server, the following steps are necessary:
Create c/${CategoryName} directory.
Create the following files:
Update c/categories.xml .
Adding a new package
A new package shall be published on the server, and here are the steps you need to do:
Check if the package category already exists, or a new category needs to be created.
Create the package directory p/${packagename}/.
Create those files:
Update the category files:
Adding a release
The time has come to release a new version of an existing package. Those are the steps to do:
Publish the release's package.xml as r/${packagename}/package.0.1.2.xml .
Create the version specific r/${packagename}/0.1.2.xml .
Update state files if appropriate: r/${packagename}/latest.txt , stable.txt , beta.txt , alpha.txt , devel.txt .
Generate r/${packagename}/deps.0.1.2.xml .
Update r/${packagename}/allreleases.xml and r/${packagename}/allreleases2.xml .
Place package archives (tar and tgz) at the place specified in r/${packagename}/0.1.2.xml .
| Changes between PEAR REST interface versions (Previous) | (Next) Packages | ||||||||
| |
|||||||||
|
|||||||||