Binary Releases

From Daya Bay
Jump to navigation Jump to search
Offline Documentation: [Offline Category] [FAQ] [Howto] [Reference] [Manual]

Offline Documentation
This article is part
of the Offline Documentation
Other pages...

Offline Category
How Tos
Getting Started
Software Installation

See also...

General Help on this Wiki

This topic describe binary release mechanisms for the offline software.


The dybbin script can help create and install binary releases or to move a release built at one location to another location. It does this by creating a tar file holding the minimal set of project and external files needed. The various functionality are exposed through a number of sub-commands described in the following subsections.

Get dybbin as you would dybinst:

 svn export

Install from Source

To create a binary release, one must first build a release from source in the usual way.

Make binary tar ball

A tar ball is made from a release and its externals. The platform-specific temporary directories in each package will not be included and only the externals needed for the release will be included. Uncompressed releases are ~3GiB, compressed tar ball is ~725MiB. The resulting tar ball filename will be printed and will look something like:

NuWa-trunk_i686-debian-gcc43-dbg.tar    (uncompressed)
NuWa-trunk_i686-debian-gcc43-dbg.tar.gz (compressed)

Environment Setup

The environment must have some basic understanding of the release to be packed. This is done with the usual first-level setup script:

cd NuWa-<release>
cd ..

If your system's Python install is too old (cough, Red Hat, cough) you will need to use the one from NuWa. To do that use the usual second-level setup script:

cd NuWa-trunk/dybgaudi/DybRelease/cmt/
cd -

The pack command

You can now make a packed tar ball. The "pack" command must be run from the directory holding the release. You can use -z to produce a compressed (gzip) tar ball. An example of building the tar ball is:

dybbin pack [-z] <release>

Unpacking a binary tar ball

Go to some new location where you want to install the binary release and run the "unpack" command. This is equivalent to just running tar directly to unpack the tar ball.

cd /path/to/some/new/area


dybbin unpack /path/to/NuWa-<release>_<cmtconfig>.tar.gz


tar -xzvf /path/to/NuWa-<release>_<cmtconfig>.tar.gz

Fix the setup scripts

There are various places where the original paths are hard coded. The "setup" command will correct these to match the current location. This command should be run after an "unpack" or if a complete release + externals are moved by some other means. It should be run from the directory holding the unpacked NuWa-<release> directory.

dybbin setup <release>

You can then use this new release as if it was built in place.

Test the release

It is probably best to start with a fresh terminal window to clear out the environment setup with dybbin.

Offline Software Documentation: [Offline Categories] [FAQ] [Offline Manual Category]