Binary bundles are created from an installation. Therefore it is simple to build a collection of packages, do some validation testing, and then wrap them up in a bundle. The following exercise shows how this is done although we will cheat by installing binary packages rather than building them from source.
Download this bundle.
Set $GPT_INSTALL_LOCATION to an empty location and run gpt-install foo-2.2.3-i686-pc-linux-gnu-bin.tar.gz
Run gpt-bundle -all -bn=newfoo -bv=1.0 -bl=2.0. This will create a bundle called newfoo-2.0-i686-pc-linux-gnu-bin.tar.gz.
Unpack the bundle into an empty directory and check the contents. You should see the following files:
The bundle definition file:
newfoo-2.0.gpt-bundle.xml
The binary packages:
globus_common-3.5-i686-pc-linux-gnu-gcc32-pgm.tar.gz globus_common-3.5-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_common_setup-2.1-i686-pc-linux-gnu-noflavor-pgm.tar.gz globus_gsi_callback-0.3-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_gsi_cert_utils-0.4-i686-pc-linux-gnu-gcc32-pgm.tar.gz globus_gsi_cert_utils-0.4-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_gsi_credential-0.5-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_gsi_openssl_error-0.2-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_gsi_proxy_core-0.3-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_gsi_proxy_ssl-0.1-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_gsi_sysconfig-0.3-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_openssl-0.10-i686-pc-linux-gnu-gcc32-pgm.tar.gz globus_openssl-0.10-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_openssl_module-0.2-i686-pc-linux-gnu-gcc32-rtl.tar.gz globus_proxy_utils-0.5-i686-pc-linux-gnu-gcc32-pgm.tar.gz globus_trusted_ca_42864e48_setup-0.5-i686-pc-linux-gnu-noflavor-pgm.tar.gz
A package list file used by older versions of GPT:
packagelist
This bundle is now ready to be installed by gpt-install.