Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gpt-query(8) [debian man page]

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

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> perl v5.14.2 2012-04-30 GPT-QUERY(8)

Check Out this Related Man Page

BUNDLE(1)																 BUNDLE(1)

NAME
bundle - Ruby Dependency Management SYNOPSIS
bundle COMMAND [--no-color] [--verbose] [ARGS] DESCRIPTION
Bundler manages an application's dependencies through its entire life across many machines systematically and repeatably. See the bundler website http://gembundler.com for information on getting started, and Gemfile(5) for more information on the Gemfile for- mat. OPTIONS
--no-color Prints all output without color --verbose Prints out additional logging information BUNDLE COMMANDS
We divide bundle subcommands into primary commands and utilities. PRIMARY COMMANDS
bundle install(1) bundle-install.1.html Install the gems specified by the Gemfile or Gemfile.lock bundle update(1) bundle-update.1.html Update dependencies to their latest versions bundle package(1) bundle-package.1.html Package the .gem files required by your application into the vendor/cache directory bundle exec(1) bundle-exec.1.html Execute a script in the context of the current bundle bundle config(1) bundle-config.1.html Specify and read configuration options for bundler bundle help(1) Displays this help page UTILITIES
bundle check(1) Determine whether the requirements for your application are installed and available to bundler bundle list(1) Show all of the gems in the current bundle bundle show(1) Show the source location of a particular gem in the bundle bundle outdated(1) Show all of the outdated gems in the current bundle bundle console(1) Start an IRB session in the context of the current bundle bundle open(1) Open an installed gem in the editor bundle viz(1) Generate a visual representation of your dependencies bundle init(1) Generate a simple Gemfile, placed in the current directory bundle gem(1) Create a simple gem, suitable for development with bundler bundle platform(1) bundle-platform.1.html Displays platform compatibility information bundle clean(1) Cleans up unused gems in your bundler directory OBSOLETE
These commands are obsolete and should no longer be used o bundle lock(1) o bundle unlock(1) o bundle cache(1) March 2013 BUNDLE(1)

Featured Tech Videos