Bundles created with versions of GPT older than 3.0 are treated differently because they are not versioned. For one thing these older bundles cannot be updated; only installed and uninstalled. Another difference is that many of the package conflicts are ignored by gpt-install to replicate the behaviour of the older GPT's. Here are some examples to illustrate the differences:
This example shows how gpt-install installs two bundles which have package conflicts. When bundle foo_dbg-2 is installed then the packages that are conflicting are ignored. The result is that the integrity of the bundle is lost. Using the -force flag causes the opposite behaviour. The installed bundle foo-2 would loose its integrity.
bash$ gpt-install foo-2.2.3-i686-pc-linux-gnu-bin.tar.gz Bundle foo-2 successfully installed. bash$ gpt-install foo_dbg-2.2.3-i686-pc-linux-gnu-bin.tar.gz Bundle foo_dbg-2 successfully installed. bash$ gpt-verify Verifying Bundles... Bundle: foo-2 Bundle: foo_dbg-2 Package globus_openssl-gcc32dbg-pgm ver: 0.10 is missing from installation Package globus_common-gcc32dbg-pgm ver: 3.5 is missing from installation Package globus_gsi_cert_utils-gcc32dbg-pgm ver: 0.4 is missing from installation Package globus_proxy_utils-gcc32dbg-pgm ver: 0.5 is missing from installation
This example shows that gpt-install still pays attention to package versions. Bundles that contain conflicting versions cannot be installed without the -force flag.
bash$ gpt-install foo-2.2.3-i686-pc-linux-gnu-bin.tar.gz Bundle foo-2 successfully installed. bash$ gpt-install fee-2.0-i686-pc-linux-gnu-bin.tar.gz Error: The following package conflicts were found: globus_common-gcc32-rtl ver: 2.0 in bundle fee-2 conflicts with globus_common-gcc32-rtl ver: 3.5 in bundle foo-2 globus_openssl-gcc32-pgm ver: 0.1 in bundle fee-2 conflicts with globus_openssl-gcc32-pgm ver: 0.10 in bundle foo-2 globus_openssl-gcc32-rtl ver: 0.1 in bundle fee-2 conflicts with globus_openssl-gcc32-rtl ver: 0.10 in bundle foo-2 globus_common-gcc32-pgm ver: 2.0 in bundle fee-2 conflicts with globus_common-gcc32-pgm ver: 3.5 in bundle foo-2 globus_common_setup-noflavor-pgm ver: 2.0 in bundle fee-2 conflicts with globus_common_setup-noflavor-pgm ver: 2.1 in bundle foo-2