1GPT-BUNDLE(8) User Contributed Perl Documentation GPT-BUNDLE(8)
2
6 gpt-bundle - Creates binary or source bundles from an installation or a
7 collection of source packages.
8
10 gpt-bundle [options] packages
11 Options:
13 -verbose Print copious output
15 -help Print usage
16 -man Print man page.
17 -version Print GPT version.
18 -srcdir=PATH Directory containing source packages
19 -tmpdir=PATH Directory used to create binary packages
20 -installdir=PATH Directory containing an installation
21 -bn=NAME Name of the bundle
22 -bv=MAJOR.MINOR Version of the bundle
23 -bs=STABILITY Stability of the bundle contents
24 -bl=VERSION Version Label of the bundle
25 -native Create bundles of native pkgs (RPMs only).
26 -all Bundle everything in the package directory..
27 -nodeps Don't include any dependent packages.
28 -nosetups Don't include dependent setup packages.
29 -template Outputs empty Bundle Def XML file.
30 -bundledef=FILE Outputs XML file with command line values.
31 -exclude=PACKAGE Don't include PACKAGE in bundle
32 -config=FILE Use bundle options stored in FILE
33 -xml=FILE XML bundle description file
34 -output=FILE Name of the bundle file,
35 -rpmprefix=PATH Absolute path encoded in the RPM.
36 -buildnumber=NUMBER Build number used for pgm_static packages
37 -rpmlicense=LABEL License Label added to the RPM header
38 [packages] List of packages to be bundled
39
41 gpt-bundle Creates binary or source bundles from an installation or a
42 collection of source packages. These bundles can then distributed be
43 installed using gpt-install or gpt-build. A bundle consists of a
44 collection of packages and a XML formatted description file. The DTD
45 for this file is found in $GPT_LOCATION/share/dtd/gpt_bundle.dtd.
46 The script accepts a list of packages from the command line or from an
48 inputed bundle description file. It expands this list to include all
49 of the packages that the listed packages depend on. It then uses this
50 expanded list to create a new bundle description file which is then
51 added to the collection of packages to form a bundle.
52 gpt-bundle assumes that all of the packages needed to create a source
54 bundle are found in one subdirectory identified by the -srcdir switch.
55 gpt-bundle assumes that all of the packages need to create a binary
57 bundle are installed in a location identified by the -installdir flag
58 or $GLOBUS_LOCATION.
59 The list of packages that can be entered from the command line are of
61 the form NAME-FLAVOR-PACKAGE_TYPE. The wildcard character '*' can also
62 be used.
63
65 -srcdir=PATH
66 Specifies where the directory containing your source packages
67 is. If this is used, a source bundle will be created. Note
68 that this flag is required to create source bundles.
69 -installdir=PATH
71 Specifies where the installation used for creating binary
72 bundles is. $GLOBUS_LOCATION is the default.
73 -xml=FILE
75 Specifies the input bundle description file. A new file will
76 be generated using the contents of this file and included in
77 the bundle.
78 -bundlename=NAME
80 The name of the bundle. This name is stored in the bundle
81 description file and used as part of the bundle filename if
82 -output is not specified.
83 -bundleversion=MAJOR.MINOR
85 This is the bundle version number. It is stored in the bundle
86 description file and used for bundle updates. It is also used
87 for the bundle filename if -bundlelabel is not specified.
88 -bundlelabel=VERSION
90 This is the bundle version label. It is stored in the bundle
91 description file as a string and so can accomodate any
92 versioning scheme. The label is used in user queries, and as
93 part of the bundle filename.
94 -bundlestability=STABILITY
96 This is the bundle version stability. It is a field that is
97 used to indicate the stability of this version of the bundle.
98 The field can have values of experimental, alpha, beta, or
99 production. The default vaule is experimental. The field is
100 stored in the bundle description file and used for user
101 queries.
102 -tmpdir=PATH
104 Specifies the where the directory is that gpt-bundle should use
105 to store generated binary packages.
106 -all Tells gpt-bundle to bundle all of the packages in the source
108 package directory or installation.
109 -native Tells gpt-bundle to also bundle packages that are in the native
111 format of the operating system. Presently this only works for
112 RPMS on linux. gpt-bundle will output two bundle giving the
113 native bundle a platform specific extension such as -rpm.
114 -nodeps Tells gpt-bundle to only include the packages specified--do not
116 check for or include dependencies.
117 -nosetups
119 Tells gpt-bundle to exclude any packages that are pulled in by
120 a setup dependencies. Note that setup packages that are listed
121 on the command line will still be added to the bundle..
122 -exclude=package1,package2,...
124 This option excludes the listed packages from the created
125 bundle. It can be specified multiple times with the final
126 listing used being an aggregate of all the listed packages.
127 This option can be abbreviated as
128 '-exclude=package1,package2,...'.
129 -output=FILE
131 This is an alternative way to specify the bundle name. The
132 output file is put in the directory from which gpt-bundle was
133 invoked if no path was given, in a directory relative it if a
134 relative path was given, or in the absolute location, if given.
135 -template
137 Creates an empty Bundle XML that can be modified and used to
138 create a new bundle.
139 -bundledef=FILE
141 Creates an XML file with name equal to FILE.gpt-bundle.xml.
142 This file will contain a GPT Bundle definition with values set
143 to those passed in on the command line.
144 -rpmprefix=<path_to_installation>
146 This should be set to the path to your GLOBUS_LOCATION. GPT
147 will use a value of "/usr/grid" if this option is not
148 specified.
149 -rpmlicense=<label>
151 Provides an alternate copyright label for the rpms. The default
152 is whatever GPT was configured with.
153 -help Print a brief help message and exits.
155 -buildnumber=<number>
157 Build number used to version static packages.
158 -man Prints the manual page and exits.
160 -version
162 Prints the version of GPT and exits.
163
165 The -bundle* switches can be used to override content in the bundle
166 definition file inputted by the -xml switch. The relationship between
167 the switches and the bundle definition file contents is shown in the
168 following table:
169 I<Switch> I<Element> I<Attribute>
171 -bundlename GPTBundleData Name
173 -bundleversion BundleReleaseInfo Major, Minor
174 -bundlelabel BundleReleaseInfo VersionLabel
175 -bundlestability VersionStability Release
176
178 gpt-bundle encourages a naming convention for bundle filenames. The
179 convention can be overriden using the -output switch. The convention
180 is as follows:
181 NAME-VERSION-src_bundle.tar.gz for source bundles
183 NAME-VERSION-ARCH-gpt.tar.gz for gpt binary bundles. ARCH is the platform ID.
184 NAME-VERSION-ARCH-rpm.tar.gz for rpm binary bundles.
185 NAME comes from the -bundlename switch. VERSION comes from the
187 -bundlelabel switch. If this switch is not used then VERSION comes
188 from the -bundleversion switch.
189 Unless overrided by the switches previously mentioned, the values for
191 can also be extracted from the bundle definition file inputted by the
192 -xml switch.
193
195 gpt-build(8) gpt-install(8) gpt-pkg(8)
196
198 Michael Bletzinger <mbletzin@ncsa.uiuc.edu>, Eric Blau
199 <blau@mcs.anl.gov> and Patrick Duda <pduda@ncsa.uiuc.edu>
200perl v5.12.3 2011-03-24 GPT-BUNDLE(8)