Pre-Grant Publication Number: 20070118658
Please help the USPTO examine the application by evaluating the relevance of the publicly submitted prior art to the patent application.
Peer To Patent forwards the Top 10 most relevant prior art submissions and their annotations to the USPTO.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Prior Art Detail
Summary / Description
| Summary / Description | A software package manager uses a distribution unit containing components for a software package and a manifest file that describes the distribution unit to manage the installation, execution, and uninstallation of software packages on a computer. |
Basic Information
| Type of Prior Art | Issued Patents - US |
| Country | United States of America |
| Patent/Application # | 6381742 |
| Kind Code | United States (US) - United STATES Patent - A |
| Patentee Name | Jonathan A. Forbes, Jeremy D. Stone, Srivatsan Parthasarathy, Michael J. Toutonghi, Michael V. Sliger |
| Relevant Pages, Columns, or Lines | claim 2 |
| URL | http://patft.uspto.gov/netacgi/... |
| Filing Date | April 30, 2002 |
| Additional Information | |
Notes / To Do
| Notes | |
Excerpt
Excerpt The method of claim 1, wherein resolving the software dependencies comprises:
acquiring, for each of the software dependencies in turn, a dependency manifest file that describes a dependency distribution unit for a dependency software package;
resolving software dependencies for the dependency software package as specified by the dependency manifest file;
acquiring the dependency distribution unit for the dependency software package;
extracting components in the dependency software package from the dependency distribution unit into a directory on the computer;
causing the installation of the dependency software package on the computer; and
updating the code store data structure on the computer with information from the dependency manifest file pertaining to the dependency software package. |
Relevance
Claims
6
Relevance
Claim Chart
All
9
Relevance
Claim Chart
All
