There are build scripts for Windows and Unix that will run the minimization tool and generate a file called EDS.zip that can be used for one-off deployments.
The Makefile in the root of the project is similar, but is used to prepare a more traditional ".tar.gz" distribution via
make dist and to perform an installation via
An RPM specfile is also present. Generating an RPM requires running the
make dist command to obtain the source tarball, and then executing
rpmbuild against it.
The formal release process is as follows:
- Check in any uncommitted changes against the trunk.
- Modify and check in Makefile and shibboleth-embedded-ds.spec with the updated version number of the release.
make distagainst the sources.
- Sign the tarball and create the md5 checksum file.
- On a Windows host, run
build.batfrom the build directory and rename the resulting file to match the tarball name except with a .zip extension.
- Sign the zipfile and create the md5 checksum file.
- Upload the six resulting files to email@example.com:/home/shibwww/html/downloads/embedded-discovery-service/version
- Point the latest symlink at the new location.
- Tag the trunk with the version number.
To build and publish RPMs:
- Login to the build service at https://build.opensuse.org/project/show?project=security%3Ashibboleth
- Create a new package called shibboleth-embedded-ds-version.
- Upload the tarball and specfile as sources for the package.