Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gpt-install(8) [debian man page]

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

NAME
gpt-install - Installs GPT packages. SYNOPSIS
gpt-install [options] [packages or bundles] Options: -verbose Print copious output -help Print usage -man Print man page. -version Print GPT version. -force Replace package no matter what. -loose Replace a broader range of packages. -installdir=PATH Override $GLOBUS_LOCATION. -tmpdir=PATH Path to tmp disk space [packages or bundles] List of binary packages and bundles to install. DESCRIPTION
gpt-install takes a GPT described package or bundle and installs it. The program can install either RPM's or GPT packages. OPTIONS
-force forces all action to be taken, regardless of state. -tmpdir Place to unpack bundles. -installdir Directory to which files shall be written. Default is $GLOBUS_LOCATION -loose pgm packages can replace a pgm_static package (and vice versa) or a pgm package with a different flavor. -help Print a brief help message and exits. -man Prints the manual page and exits. -version Prints the version of GPT and exits. EXAMPLES
For the command: gpt-install foo-2.1-gcc32-pgm.tar.gz foo-1.1-gcc32-pgm will be replaced. foo-2.2-gcc32-pgm will B<not> be replaced. It is newer. foo-1.1-vendorcc32-pgm will B<not> be replaced. Wrong flavor. foo-1.1-gcc32-pgm_static will B<not> be replaced. Wrong package type foo-2.2-gcc32-pgm_static will B<not> be replaced. Wrong package type For the command: gpt-install -force foo-2.1-gcc32-pgm.tar.gz foo-1.1-gcc32-pgm will be replaced. foo-2.2-gcc32-pgm will be replaced. foo-1.1-vendorcc32-pgm will B<not> be replaced. Wrong flavor foo-1.1-gcc32-pgm_static will B<not> be replaced. Wrong package type foo-2.2-gcc32-pgm_static will B<not> be replaced. Wrong package type For the command: gpt-install -loose foo-2.1-gcc32-pgm.tar.gz foo-1.1-gcc32-pgm will be replaced. foo-2.2-gcc32-pgm will B<not> be replaced. It is newer. foo-1.1-vendorcc32-pgm will be replaced. foo-1.1-gcc32-pgm_static will be replaced. foo-2.2-gcc32-pgm_static will B<not> be replaced. It is newer. For the command: gpt-install -force -loose foo-2.1-gcc32-pgm.tar.gz foo-1.1-gcc32-pgm will be replaced. foo-2.2-gcc32-pgm will be replaced. foo-1.1-vendorcc32-pgm will be replaced. foo-1.1-gcc32-pgm_static will be replaced. foo-2.2-gcc32-pgm_static will be replaced. BUGS
gpt-install currently does not honor static build numbers. Instead it will replace any pgm_static package that is the same version or older. For example: gpt-install -force foo-2.1-2-gcc32-pgm_static.tar.gz foo-1.1-5-gcc32-pgm_static will be replaced. foo-2.1-1-gcc32-pgm_static will be replaced. foo-2.1-5-gcc32-pgm_static will be replaced. foo-2.2-1-gcc32-pgm_static will not be replaced. foo-2.1-gcc32-pgm will not be replaced. SEE ALSO
gpt-uninstall(1) gpt-query(1) gpt-verify(1) AUTHOR
Michael Bletzinger <mbletzin.ncsa.uiuc.edu> and Eric Blau <eblau.ncsa.uiuc.edu> perl v5.14.2 2012-04-30 GPT-INSTALL(8)

Check Out this Related Man Page

GIT-REPLACE(1)							    Git Manual							    GIT-REPLACE(1)

NAME
git-replace - Create, list, delete refs to replace objects SYNOPSIS
git replace [-f] <object> <replacement> git replace -d <object>... git replace -l [<pattern>] DESCRIPTION
Adds a replace reference in refs/replace/ namespace. The name of the replace reference is the SHA-1 of the object that is replaced. The content of the replace reference is the SHA-1 of the replacement object. Unless -f is given, the replace reference must not yet exist. Replacement references will be used by default by all Git commands except those doing reachability traversal (prune, pack transfer and fsck). It is possible to disable use of replacement references for any command using the --no-replace-objects option just after git. For example if commit foo has been replaced by commit bar: $ git --no-replace-objects cat-file commit foo shows information about commit foo, while: $ git cat-file commit foo shows information about commit bar. The GIT_NO_REPLACE_OBJECTS environment variable can be set to achieve the same effect as the --no-replace-objects option. OPTIONS
-f If an existing replace ref for the same object exists, it will be overwritten (instead of failing). -d Delete existing replace refs for the given objects. -l <pattern> List replace refs for objects that match the given pattern (or all if no pattern is given). Typing "git replace" without arguments, also lists all replace refs. BUGS
Comparing blobs or trees that have been replaced with those that replace them will not work properly. And using git reset --hard to go back to a replaced commit will move the branch to the replacement commit instead of the replaced commit. There may be other problems when using git rev-list related to pending objects. And of course things may break if an object of one type is replaced by an object of another type (for example a blob replaced by a commit). SEE ALSO
git-tag(1) git-branch(1) git(1) GIT
Part of the git(1) suite Git 1.8.3.1 06/10/2014 GIT-REPLACE(1)
Man Page