NAME
gpt-query - Queries an installation for packages
SYNOPSIS
gpt-query [-name=Name -flavor=Flavor -pkgtype=Type --help -file=name
-man -deps=run|sdk] [pkgname-flavor-pkgtype+]
DESCRIPTION
gpt-query searches installed packages for matches to the query. Name
is the name of the package. Flavor is the information about linking and
compile options used on package. Type is the type of the package. ?
will alow the use to access system help.
The user may enter a value for any of the options. These options can
be used in combination or not at all. The script will take the options
being used and try to find all matching items.
An alternate form is to use the pkgname-flavor-pkgtype tuples.
Multiple of instances of these tuples can be used in a query.
OPTIONS
-name=NAME
Returns all of the packages matching NAME.
-flavor=FLAVOR
Returns all of the packages matching FLAVOR.
-pkgtype=TYPE
Returns all of the packages matching TYPE.
-file=FILE
Returns the package owning the FILE. FILE needs to be either an
absolute path or referenced to $GLOBUS_LOCATION.
-deps=run|sdk
Returns the runtime or build dependencies of a package.
-help
Print a brief help message and exits.
-man
Prints the manual page and exits.
-version
Prints the version of GPT and exits.
-what-bundles
Prints a list of the installed bundles.
-verify-bundle=BUNDLE
Takes a bundle defintion and checks to see if it matches the
installation.
-bundle-packages=BUNDLE
List the packages that belong to the desired bundle.
-bundle BUNDLE 1 [BUNDLE 2]
If two bundles are given, the bundles will be compared to one
another for equality. If only one bundle is given, the bundle will
be checked against the installation. This command works on tar
bundles.
EXAMPLES
gpt-query
Returns a listing of all of the installed packages.
gpt-query -name=foo
Returns all flavors and package types with the name "foo".
gpt-query foo
Also returns all flavors and package types with the name "foo".
gpt-query 'foo-*-*'
A third way of typing the same query. Note the single quotes.
gpt-query '*-noflavor-*'
List all of the packages with a ’noflavor’ build flavor.
gpt-query -file=libexec/globus-build-env-gcc32.sh
Returns "/libexec/globus-build-env-gcc32.sh is owned by
globus_core-gcc32-rtl"
gpt-query -file=$GLOBUS_LOCATION/libexec/globus-build-env-gcc32.sh
Returns the same.
gpt-query -file=globus-build-env-gcc32.sh
Returns an error because the path is incorrect.
OUTPUT
Here is an example output:
gpt-query '*-noflavor-*'
4 packages were found in /home/mbletzin/work/install that matched your query:
packages found that matched your query
globus_core-noflavor-data ver: 2.1 cmp id: 2.1.0
globus_core_setup-noflavor-pgm ver: 2.0 cmp id: 2.0.0
globus_ssl_utils-noflavor-data ver: 2.1 cmp id: 2.1.0
kca_setup-noflavor-pgm ver: 3.0.2p1 cmp id: 1.0.0
For each package name, flavor, package type, version, and the
compatibility identifier is return. The compatibility identifier is
what is used to resolve dependencies.
SEE ALSO
gpt-install(8) gpt-uninstall(8) gpt-verify(8) gpt-postinstall(8)
AUTHOR
Michael Bletzinger <mbletzin.ncsa.uiuc.edu> and Eric Blau
<eblau.ncsa.uiuc.edu>