The GPT build tools can aid in determining packaging dependencies for build, installing and troubleshooting. The tools can generate three dependency types, install, build and none. 'install' will list all packages necessary for a successful install of the given package. Note that this list does not include setup package dependencies. This is due to the nature of setup dependencies, the package name cannot be inferred from the setup dependency name. The 'build' dependency type will list all packages necessary to build the given package in build dependent order. The 'none' dependency implies that -deptype is not specified in which case only the dependencies explicitly listed in the package's data file are printed.

The listings can be generated from any combination of the given source tree (-srcdir) and the given package directory (-pkgdir). The source tree is tried first, if the given package is not found, the available packages are searched followed by the available bundles.

> uberBuild -listdeps -srcdir=/sandbox globus_gsi_proxy_core
globus_gsi_proxy_ssl
globus_gsi_openssl_error
globus_openssl
globus_common
globus_gsi_credential
globus_gsi_sysconfig
globus_gsi_cert_utils
globus_openssl_module

> uberBuild -listdeps -deptype=build -srcdir=/sandbox globus_gsi_proxy_core
globus_common
globus_openssl
globus_openssl_module
globus_gsi_openssl_error
globus_gsi_cert_utils
globus_gsi_sysconfig
globus_gsi_proxy_ssl
globus_gsi_callback
globus_gsi_credential