|
I can provide a bit of background on why this sometimes happens.
In a fixpack, typically a set of plugins are updated. Also, the list of
plugins which correspond to an installable feature (shown in Installation
Manager, e.g. RPG and COBOL Tools) could be updated.
If an updated plugin has new dependencies, the new dependencies will also
have to be installed even if they were not changed in the fixpack. e.g.
Plugin A depends on B, C, and D. In the fixpack, plugin A now depends on
B, C, D, and E. When the fixpack is installed, the updated A plus the
unchanged E would have to be installed (possibly requiring another disk
image).
If the list of plugins which correspond to an installable feature is
updated, the plugins added to the list would have to be installed even if
they were not actually changed in the fixpack. e.g. Plugin A is installed
by installable feature X. In the fixpack, plugin A is now installed by
installable feature Y as well. A user with installable feature Y only
would not have plugin A on their first install but the fixpack would
install it (possibly requiring another disk image).
Note: this is a very high-level view of the process with lots of details
omitted.
Note2: the disk images in ESS are organized differently then in Passport
Advantage, so 'disk2' in ESS is not the same as 'disk2' in Passport. The
same content is provided.
Thanks,
Eric
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.