Host-specific information is generated by the various setup packages when gpt-postinstall is invoked by the "make install" step. (The source installer is a wrapper around the GPT tools.)
If you generate binary packages, as Joe suggested, it will package the setup scripts, but not the host-specific results of the setup scripts. You will then run gpt-postinstall after installing the binary packages on your additional servers. You can force all setup scripts can be re-run by running "gpt-postinstall -force" ----- "Arn" <[email protected]> wrote: > > > > gpt-pkg creates binary packages from an installation. The command > > > > gpt-pkg -all > > > > will generate a binary package for each that you have installed in > $GLOBUS_LOCATION > > > > Doc for gpt-pkg is available at: > http://grid.ncsa.illinois.edu/gpt/man/latest-stable/index.html > > > > Thanks, but what happens to all the host specific info that is > included in many files during the install ? i.e. during "make" and > "make install" > My worry is that if I create a package from an install on one server > , > all the host specific info in the install will break GT when > installed > from package on another server.
