Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gpt-verify(8) [debian man page]

GPT-VERIFY(8)						User Contributed Perl Documentation					     GPT-VERIFY(8)

gpt-verify - Verify dependencies needed for Globus are avaliable. SYNOPSIS
gpt-verify [ -sdk -bundle -help -version -man ] DESCRIPTION
gpt-verify is used to verify both runtime and setup dependencies along with setup packages for the current Globus installation. gpt-verify will serach through the list of dependencies and make sure that each is met. If a problem is found, gpt-verify will exit with an error and list missing files. OPTIONS
-sdk: Verify build dependencies. -bundle Verify installed bundles only. -help Print a brief help message and exits. -man Prints the manual page and exits. -version Prints the version of GPT and exits. SEE ALSO
gpt-install(8) gpt-uninstall(8) gpt-query(8) gpt-postinstall(8) AUTHOR
Michael Bletzinger <> and Eric Blau <> perl v5.14.2 2012-04-30 GPT-VERIFY(8)

Check Out this Related Man Page

GPT-PKG(8)						User Contributed Perl Documentation						GPT-PKG(8)

gpt-pkg - Creates flavored binary packages out of an installation SYNOPSIS
gpt-pkg [options] packages Options: -verbose Print copious output -help Print usage -man Print man page. -version Print GPT version. -native Create native pkgs as well as GPT pkgs (RPMs only). -all Archive everything in the package directory.. -installdir=PATH Override $GLOBUS_LOCATION -pkgdir=PATH Directory to put the packages -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 archived DESCRIPTION
gpt-pkg Creates binary packages from an installation. The installation needs to contain GPT packaging data files. An installation is created by running gpt-build on a collection of source packages or bundles. FILES IN PGM PACKAGES
Installed files such as executables that are found in pgm and ptm_static packages will overwrite one another when multiple flavors of the same package are built by gpt-build. To preserve multiple flavors of these files, gpt-build copies them into flavored subdirectories. For example, the program $GLOBUS_LOCATION/bin/foo will be copied into the location $GLOBUS_LOCATION/bin/gcc32/shared if it was built with dynamically with the gcc32 flavor. gpt-pkg retrieves these files and copies them back to their proper location before packaging them. Thus gpt-pkg will also overwrite these files as it archives the different flavors of a pgm package. OPTIONS
-installdir Specify the directory in which the installed files currently live. If this argument is not supplied, the value of the environment variable GLOBUS_LOCATION is used instead. -all Packages all of the binaries in an installation. -native Creates a package in the native packaging format. Currently only rpm is supported. -rpmprefix=<path_to_installation> This should be set to the path to your GLOBUS_LOCATION. GPT will use a value of "/usr/grid" if this option is not specified. -rpmlicense=<label> Provides an alternate copyright label for the rpms. The default is whatever GPT was configured with. -verbose Prints out all of the build messages. -log=FILE Appends all of the build messages to FILE. This option also sets -verbose. -help Print a brief help message and exits. -man Prints the manual page and exits. -version Prints the version of GPT and exits. pgm and pgm_static packages gpt-build copies the files for these packages in a flavored location because different flavors of these types of packages will conflict with each other. gpt-pkg restores these files when it packages pgm and pgm_static types. SEE ALSO
gpt-bundle(8) gpt-install(8) gpt-build(8) AUTHOR
Michael Bletzinger <> and Eric Blau <> perl v5.14.2 2012-04-30 GPT-PKG(8)

Featured Tech Videos