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
GPT-BUILD(8) User Contributed Perl Documentation GPT-BUILD(8) NAME
gpt-build - Builds and installs GPT source packages and bundles. SYNOPSIS
gpt-build [options] [macros] [source packages] flavors ... Options: -verbose Print copious output -help Print usage -man Print man page. -version Print GPT version. -installdir=path_to_installation Override $GLOBUS_LOCATION -builddir=path_to_build directory Directory to unpack tarfiles -logdir=log_file_directory Directory for package logs -srcdir=source_directory Directory containing a source package -static Build static executables -force Force rebuilds -update Rebuild if newer -disable-version-checking Ignore versions in package dependencies. -std-flavors Build all std flavors. -all-flavors Build all of the flavors -coresrc Override installed globus_core pkg -nosrc Only install the flavors [macro=value] Macro definitions [list of flavors to build] Flavors that define the build options [list of source packages] Tarfiles of source bundles or packages DESCRIPTION
gpt-build Builds and installs software from source distributions. The script reads the build instructions for each source distribution from a package metadata file called pkg_data_src.gpt. If no instructions are found the script uses the default instructions described in Grid::GPT::PkgMngmt::Build. Multiple packages can be built by passing in multiple -srcdir arguments or multiple source packages and or bundles. For now these have to be passed in in dependent order ie. if package foo needs package fee's headers to build then fee should come first. gpt-build does not create binary packages as globus-build does. This is done by a seperate script called gpt-pkg. FLAVORS
Build flavors are character string labels that represent a set of compiler and linker options defined during the building of the globus_core package. Packages can be built with any installed flavor. globus_core can only be built with pre-defined flavors. globus_core needs to be built by hand (i.e. ./configure|make|make install) to install a custom build flavor. FILES IN PGM PACKAGES
Installed files such as executables that are found in pgm and pgm_static packages will overwrite one another when multiple flavors of the same package are built. Thus only the files from the last flavor built will be present after a gpt-build run. To preserve multiple flavors of these files, they are automatically copied 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. These files are retrieved by gpt-pkg. OPTIONS
-srcdir Specifies the where the source directory is. This is used by developers to build out of a repository.. -installdir Specifies the where the install directory is. This directory will be where the targets are installed before being archived. Note that this directory needs contain the installation targets of all of the packages which satisfy build dependencies in addition to the installation targets of the package being built. Because of this, installation targets are not removed after the package is archived. Because different flavors of program packages conflict with each other, the last flavor built is the flavor of the installed files. For each flavor, gpt-build makes a copy of each installed file in a program package and puts the copy in a flavored subdirectory. -builddir Specifies the where the source tar files should be untarred and the code is built. -force Tells gpt-build to rebuild a package even if it is already installed. The default behavior is to skip any packages that have been built before. -update Tells gpt-build to build even if an older version is installed. -verbose Prints out all of the build messages. -std-flavors Build the globus_core package with all of the flavor choices marked as standard in the flavor configuration file. All of the other packages will be built with all of the flavors sucessfully installed by globus_core. -all-flavors Build the globus_core package with all of the flavor choices marked as standard in the flavor configuration file. All of the other packages will be built with all of the flavors sucessfully installed by globus_core. -nosrc Just install the listed flavors. Don't build any source code. -coresrc Use this version of globus_core source rather than the one found in ${datadir}/globus/gpt/globus_core-src.tar.gz -flavor-cfg=FILE Use the flavor configurations found in FILE. The default configuration file is ${datadir}/globus/gpt/globus_flavor_labels.conf -logdir=DIRECTORY Store package logs of build messages in DIRECTORY. This option also sets -verbose. The default directory is ./logs. -help Print a brief help message and exits. -man Prints the manual page and exits. -version Prints the version of GPT and exits. MACROS
Build macros are perl routines and variables that are used by gpt-build while building packages. These macros are embedded in the build instructions part of the package's metadata file. Some of these macros can be set from the command line using the following format: <NAME>_GPTMACRO='new value' Note that even though this feature seems extremely flexible, it has not been thoroughly tested mainly because the authors have not been able to figure out what people will want to do with these macros. Further details are found in the Grid::GPT::PkgMngmt::BuildMacros manpage. SEE ALSO
gpt-pkg(8) gpt-bundle(8) gpt-install(8) BuildMacros(3) AUTHOR
Michael Bletzinger <mbletzin.ncsa.uiuc.edu> and Eric Blau <blau.mcs.anl.gov> perl v5.14.2 2012-04-30 GPT-BUILD(8)