On Feb 16, 2009, at 9:10 AM, Marco Lackovic wrote:
On Thu, Aug 21, 2008 at 3:02 PM, Charles Bacon <[email protected]>
wrote:
One easy thing to do is to just run configure/make, then create a
tarfile of
the installation location. You can untar it on other machines and
run
$GLOBUS_LOCATION/sbin/gpt-postinstall.
Is it possible to create a binary installer for one's own distribution
equal to the installers available at the Globus web site?
Yes. A tarball created before running make install is almost the
same. If you want it to be exactly the same, check out packaging/
from the appropriate tag of CVS (like globus_4_0_8 or globus_4_2_1)
from :pserver:[email protected]:/home/globdev/CVS/globus-
packages. Running the fait_accompli/bundle-binaries script with the
$GLOBUS_LOCATION and a path to the Makefile.in will create a binary
installer just like how we do it.
Is it possible to create a repository for a software package manager
(like yum or apt-get) in order to automate the Globus Toolkit
installation procedure as much as possible?
Once created the tarfile, or the binary installer, or the repository
for a software package manager, is it allowed to make it publicly
available?
Sure. The license we use allows for you to use GT however you want,
including making your own binary installers (of whatever kind)
available for others to use. For instance, the VDT (vdt.cs.wisc.edu)
packages Globus differently than we do and redistribute it to a pretty
large community. The NorduGrid team has made RPMs out of a subset of
GT for their use, and are working with Fedora to get them distributed
in public RPM repositories.
Charles
