Multiple-package installation with package dependencies

• US 5,721,824 A
• Filed: 04/19/1996
• Issued: 02/24/1998
• Est. Priority Date: 04/19/1996
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Taylor, Julian S.
• Primary Examiner(s): SIPOS, JOHN
• Application Number:
  US08/635,329
• Time in Patent Office: 676 Days
• Field of Search: 395/200.33, 395/200.5, 395/200.51, 395/200.52, 395/670, 395/703, 395/712
• US Class Current: 709/203
• CPC Class Codes: G06F 8/61 Installation

Abstract

Installation of a multi-package distribution software pack is split into installation of each dominant, or primary, package and installation of the dependent, or secondary, packages dependent on that dominant package. The dependent packages are installed before or after installation of the dominant package depending upon the constraints of the target system for the installation. As the dominant package is installed or delayed for later installation, an action list of dependent packages to be installed is built, and a trailer script executable by the installation utility is created to install the dependent packages on the action list. Since a dependent package may also be a dominant package, the flow of operations in the invention are layered to add additional entries on the action list for additional dependent packages dependent from a dominant package that is dependent from another dominant package.

Claims

1. A method for installing a plurality of software packages in a computing system, at least one of the software packages being dependent on a dominant software package, said method comprising the computer implemented steps of:

reading for each dominant package to be installed the dependency list for the dominant package, said dependency list identifying dependent packages that the dominant package is dependent upon;

if the dominant package has a dependent package not already installed, constructing a trailer script process and an action list, said action list having action entries, each action entry identifying a package, said trailer script process controlling installation of packages on the action list;

adding to the action list the dependent package not already installed; and

installing the dominant package and dependent packages.

2. The method of claim 1 wherein said installing step comprises the steps of:

adding an entry for the dominant package at the end of the action list;

calling the trailer script process to install the dependent packages and the dominant package on the action list.

3. The method of claim 1 wherein said installing step comprises the steps of:

installing the dominant package;

calling the trailer script process to install the dependent packages on the action list.

4. The method of claim 3 wherein said trailer script process comprises the steps of:

detecting an action entry on the action list; and

installing the dependent package identified by the action entry.

5. The method of claim 4 wherein said trailer script process further comprises the steps of:

deleting from the action list the action entry for the dependent package installed by said step of installing the dependent package; and

clearing the trailer script and the action list from the computing system if said detecting step detects an empty action list.

6. The method of claim 3 further comprising the steps of:

testing whether the dependent package, identified by the action entry from the action list, is also a dominant package having additional dependent packages;

identifying the additional dependent packages and adding action entries on the action list for the additional dependent package;

installing the dependent package having additional dependent packages; and

deleting from the action list the action entry for the dependent package having additional dependent packages.

7. The method of claim 3 further comprising the steps of:

detecting whether the dominant package has a dependency list of dependent packages;

if there is a dependency list, reading a dependency entry identifying a dependent package;

checking if the dependent package has been installed;

if the dependent package has not been installed adding an action entry on the action list for the dependent package;

if the dependent package has been installed, reading the next dependency entry on the dependency list;

detecting when all action entries for the dependent packages for the dominant package have been listed on the action list; and

installing the dominant package.

8. Apparatus for installing a plurality of software packages in a computing system, the computing system having a processor, an input/output device, and a data storage device, at least one of the software packages being dependent on a dominant software package, said apparatus comprising:

a test module testing whether or not a dominant package to be installed has dependent packages to be installed;

the dominant package being dependent on the dependent packages for successful operation;

a construct module constructing an action list if said test module indicates the dominant package has a dependent package not already installed, said action list having action entries, each action entry identifying a package to be installed;

a trailer script module controlling installation of packages on the action list;

an action entry add module adding to the action list the dependent package not already installed; and

an install module installing the dominant package and calling the trailer script module to install packages on the action list.

9. The apparatus of claim 8 wherein said install module comprises:

said action entry add module adding an entry for the dominant package at the end of the action list;

said trailer script module, when called by the install module, installing the dependent packages and the dominant package identified on the action list.

10. The apparatus of claim 8 wherein said install module comprises:

a primary install module installing the dominant package directly;

said trailer script module, when called by said install module, installing the dependent packages identified on the action list.

11. The apparatus of claim 10 wherein said trailer script module comprises:

a detection module detecting an action entry on the action list; and

an action entry install module installing the dependent package identified by the action entry.

12. The apparatus of claim 11 wherein said trailer script module further comprises:

a delete module deleting from the action list the action entry for the dependent package installed by said action entry install module.

13. The apparatus of claim 10 further comprising:

a dependency check module checking whether the dependent package, identified by the action entry from the action list, is also a dominant package having additional dependent packages;

said action entry add module identifying the additional dependent packages and adding action entries on the action list for the additional dependent packages;

said action entry install module installing the dependent package having additional dependent packages; and

said delete module deleting from the action list the action entry for the dependent package having additional dependent packages.

14. A computer program storage medium readable by a computing system and encoding a computer program of instructions for executing a computer process for installing a plurality of software packages in the computing system, at least one of the software packages being dependent on a primary software package, said computer process comprising the steps of:

reading for each primary package to be installed the dependency list for the primary package, said dependency list identifying secondary packages that the primary package is dependent upon;

if the primary package has a secondary package not already installed, constructing a trailer script process and an action list, said action list having action entries, each action entry identifying a package, said trailer script process controlling installation of packages on the action list;

adding to the action list the secondary package not already installed; and

installing the primary package and secondary packages.

15. The computer program storage medium of claim 14 where, in the computer program, the computer process step of installing comprises the steps of:

adding an entry for the primary package at the end of the action list;

calling the trailer script process to install the secondary packages and the primary package on the action list.

16. The computer program storage medium of claim 14 where, in the computer program, the computer process step of installing comprises the steps of:

installing the primary package;

calling the trailer script process to install the secondary packages on the action list.

17. The computer program storage medium of claim 16 where, in the computer program, the trailer script process comprises the steps of:

detecting an action entry on the action list; and

installing the secondary package identified by the action entry.

18. The computer program storage medium of claim 16 where said computer process in the computer program further comprises the steps of:

testing whether the secondary package, identified by the action entry from the action list, is also a primary package having additional secondary packages;

identifying the additional secondary packages and adding action entries on the action list for the additional secondary package;

installing the secondary package having additional secondary packages; and

deleting from the action list the action entry for the secondary package having additional secondary packages.

19. The computer program storage medium of claim 16 where said computer process in the computer program further comprises the steps of:

detecting whether the primary package has a dependency list of secondary packages;

if there is a dependency list, reading a dependency entry identifying a secondary package;

checking if the secondary package has been installed;

if the secondary package has not been installed adding an action entry on the action list for the secondary package;

if the secondary package has been installed, reading the next dependency entry on the dependency list;

detecting when all action entries for the secondary packages for the primary package have been listed on the action list; and

installing the primary package.