Prequisites and assumptions
- You're using vknecht's build script.
- A GPG key - needed to sign the feed.
- If you plan to update the "official" celstart feeds, upload access to crystalspace3d.org.
If you haven't done so, upload the archive with the build to the download site.
Editing the 0install feed
- Next, open $CEL/scripts/0install/celstart-runtime-1.9.xml with 0publish-gui.
- Choose "Add archive", and add the one with the new build.
- In the settings dialog coming up after that
- leave things as they are, maybe adjust the version
- for builds off Subversion it's <CS/CEL major>.<CS/CEL minor>.<CS rev>.<CEL rev>, eg. 1.9.31128.3703
- You should change the signing key to your key as well
- leave things as they are, maybe adjust the version
- Save and exit 0publish-gui.
- Copy the dependencies over:
- I do that with 0publish and a text editor, e.g. EDITOR=scite 0publish -e celstart-runtime-1.9.xml.
- Make sure the implementation for the newly added archive has all necessary attributes set.
- Copy over the requirements.
- Save and upload at http://www.crystalspace3d.org/0install/
- Next, update celstart-launcher-1.9.xml.
- Currently I create a new wrapper script for each release ... there may be a better way, tho, feel free to explore.
- First, generate a wrapper script using wrap-celstart-launcher.sh in scripts/0install/.
- Invoke like ./wrap-celstart-launcher.sh <build-version>. The result is the file celstart-launcher-<build-version>.tar.lzma. Upload it at http://www.crystalspace3d.org/0install/
- Once you have that, update celstart-launcher-1.9.xml in a fashion similar to the one described above.
- Make sure you "require" the new build for the new celstart-launcher version.
- First, generate a wrapper script using wrap-celstart-launcher.sh in scripts/0install/.
- Currently I create a new wrapper script for each release ... there may be a better way, tho, feel free to explore.
- svn commit $CEL/scripts/0install/celstart-runtime-1.9.xml $CEL/scripts/0install/celstart-launcher-1.9.xml
