[Bug 453848] Review Request: globus-core - Globus Toolkit - Globus Core

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=453848





--- Comment #3 from Mattias Ellert <mattias.ellert at fysast.uu.se>  2008-09-22 03:23:50 EDT ---
The globus alliance no longer provides tar files for sources for individual
packages in their releases on their website. Instead, the sources for all the
packages in the release are bundled together in a big monolithic tar file:

http://www-unix.globus.org/ftppub/gt4/4.2.0/installers/src/gt4.2.0-all-source-installer.tar.bz2

This monolithic thing currently contains the sources for 294 packages.

In my source RPMs I do not include this big tarfile as source. I would find it
to be an extreme waste of disk space and bandwidth if this tarfile would have
to be included in every source package since only one 294th of it is actually
used for the build. Instead I have extracted the relevant subdirectory for each
package into a per-package tar file. Which of course means that there is no URL
pointing to this exact file on the upstream website.

For between-release-updates the globus alliance do provide per-package tar
files:

http://www-unix.globus.org/ftppub/gt4/4.2.0/updates/src/

For these updated packages the provided tar files can be used with no problem.
For the non-updated packages I extract this kind of per-package tar files from
the monolithic source tree.

The globus build for each package requires that the other globus packages that
it depends on are already installed. So putting all the globus packages in one
source RPM and build as sub packages is not really possible without reworking
completely the way internal globus dependencies are handled.

(If you use the globus build script it pretends to first do "make" for all
packages and then "make install" for all packages, but in this case the "make"
is actually "make" followed by "make install" and "make install" is only post
installation configuration.)

The "Automatically generated" is just a print statement in a perl script I have
written to convert the globus XML build instructions to an RPM spec. If you
just don't like the wording I can change it to whatever you like, including the
customary "Initial build". For most packages the perl script generated spec
does not require further polishing, but occasionally some manual tweaks are
needed. I would still consider myself, and not the script, as being the
packager.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.