System and method for extraction and creation of application meta-information within a software application repository

• US 20060020937A1
• Filed: 07/21/2005
• Published: 01/26/2006
• Est. Priority Date: 07/21/2004
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Softricity (Microsoft Corporation)
• Inventors: Schaefer, Stuart
• Application Number:
  US11/186,630
• Publication Number:
  US 20060020937A1
• Time in Patent Office: Days
• US Class Current: 717/175
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

Methods for automating the detection and use of dependent software packages on a target machine include during the installation or execution of a first software package, detecting a dependency, pausing the installation or execution of the software package, configuring the dependent software package, and continuing the installation or execution of the first software package. The step of detecting the dependency includes the step of querying one or more repositories for the dependency. Further, the step of detecting the dependency includes the use of rules for template matching, or querying one or more repositories for matching configuration information. The step of detecting the dependency includes execution of a software operation on the target machine wherein a resultant failure indicates the need to query a repository. Information indicative of the configuration of the dependent software package is added to a preconfiguration snapshot of the target machine. The step of configuring the dependent software package on the target machine is performed by simulation or virtual installation. This step includes updating one or more repositories of the configuration and dependencies of the first software package. The method further includes updating one or more repositories of the configuration and dependencies of the first software package.

Claims

1. A method for automating the detection and use of dependent software packages on a target machine, the method comprising:

during the installation or execution of a first software package, detecting a dependency;

pausing the installation or execution of the software package;

configuring the dependent software package; and

continuing the installation or execution of the first software package.

2. The method of claim 1, wherein the step of detecting the dependency comprises the step of querying one or more repositories for the dependency.

3. The method of claim 2, wherein the step of detecting the dependency comprises the use of rules for template matching.

4. The method of claim 2, wherein the step of detecting the dependency comprises a query to one or more repositories for matching configuration information.

5. The method of claim 1, wherein the step of detecting the dependency comprises execution of a software operation on the target machine wherein a resultant failure indicates the need to query a repository.

6. The method of claim 1, wherein the step of detecting the dependency comprises searching a set of configured assets of the first software package.

7. The method of claim 1, wherein the step of configuring the dependent software package on the target machine comprises an installation of the dependent software package.

8. The method of claim 1, wherein information indicative of the configuration of the dependent software package is added to a preconfiguration snapshot of the target machine.

9. The method of claim 1, wherein the step of configuring the dependent software package on the target machine is performed by simulation or virtual installation.

10. The method of claim 1, wherein the step of configuring the dependent software package comprises updating one or more repositories of the configuration and dependencies of the first software package.

11. The method of claim 1, further comprising updating one or more repositories of the configuration and dependencies of the first software package.

12. A method for automating the detection and use of dependent software packages on a target machine, the method comprising:

searching a set of installation assets of a first software package for indication of dependency upon one or more other dependent software packages; and

configuring the dependent software package.

13. The method of claim 12, wherein the step of searching comprises pattern matching of information contained within the installation assets.

14. The method of claim 12, wherein the step of searching comprises using code analysis methods.

15. A system for creating a software repository comprising:

a software package asset store;

a metadata store; and

an integration engine.

16. The system of claim 15, further comprising a rule or templating engine for querying the contents of the package asset store, metadata store, and dependencies therein.

17. The system of claim 15, wherein a client of the repository can directly query for the existence of software package assets and/or dependent packages.

18. The system of claim 15, wherein the repository comprises two or more repositories operating remotely to each other.

19. The system of claim 18, wherein one repository is co-located with the client of the other repository system.