gpt-bundle - Creates binary or source bundles from an installation or a collection of source packages.
gpt-bundle [options] packages
Options:
-verbose Print copious output -help Print usage -man Print man page. -version Print GPT version. -srcdir=PATH Directory containing source packages -tmpdir=PATH Directory used to create binary packages -installdir=PATH Directory containing an installation -bn=NAME Name of the bundle -bv=MAJOR.MINOR Version of the bundle -bs=STABILITY Stability of the bundle contents -bl=VERSION Version Label of the bundle -native Create bundles of native pkgs (RPMs only). -all Bundle everything in the package directory.. -nodeps Don't include any dependent packages. -nosetups Don't include dependent setup packages. -template Outputs empty Bundle Def XML file. -bundledef=FILE Outputs XML file with command line values. -exclude=PACKAGE Don't include PACKAGE in bundle -config=FILE Use bundle options stored in FILE -xml=FILE XML bundle description file -output=FILE Name of the bundle file, -rpmprefix=PATH Absolute path encoded in the RPM. -buildnumber=NUMBER Build number used for pgm_static packages -rpmlicense=LABEL License Label added to the RPM header [packages] List of packages to be bundled
gpt-bundle Creates binary or source bundles from an installation or a collection of source packages. These bundles can then distributed be installed using gpt-install or gpt-build. A bundle consists of a collection of packages and a XML formatted description file. The DTD for this file is found in $GPT_LOCATION/etc/gpt_bundle.dtd.
The script accepts a list of packages from the command line or from an inputed bundle description file. It expands this list to include all of the packages that the listed packages depend on. It then uses this expanded list to create a new bundle description file which is then added to the collection of packages to form a bundle.
gpt-bundle assumes that all of the packages needed to create a source bundle are found in one subdirectory identified by the -srcdir switch.
gpt-bundle assumes that all of the packages need to create a binary bundle are installed in a location identified by the -installdir flag or $GLOBUS_LOCATION.
The list of packages that can be entered from the command line are of the form NAME-FLAVOR-PACKAGE_TYPE. The wildcard character '*' can also be used.
The -bundle* switches can be used to override content in the bundle definition file inputted by the -xml switch. The relationship between the switches and the bundle definition file contents is shown in the following table:
I<Switch> I<Element> I<Attribute>
-bundlename GPTBundleData Name -bundleversion BundleReleaseInfo Major, Minor -bundlelabel BundleReleaseInfo VersionLabel -bundlestability VersionStability Release
gpt-bundle encourages a naming convention for bundle filenames. The convention can be overriden using the -output switch. The convention is as follows:
NAME-VERSION-src_bundle.tar.gz for source bundles NAME-VERSION-ARCH-gpt.tar.gz for gpt binary bundles. ARCH is the platform ID. NAME-VERSION-ARCH-rpm.tar.gz for rpm binary bundles.
NAME comes from the -bundlename switch. VERSION comes from the -bundlelabel switch. If this switch is not used then VERSION comes from the -bundleversion switch.
Unless overrided by the switches previously mentioned, the values for can also be extracted from the bundle definition file inputted by the -xml switch.
gpt-build(1) gpt-install(1) gpt-pkg(1)
Michael Bletzinger <mbletzin@ncsa.uiuc.edu>, Eric Blau <blau@mcs.anl.gov> and Patrick Duda <pduda@ncsa.uiuc.edu>