Industrial application package management
A system for industrial application package management includes a computing device having a processor and a memory having executable programs and applications stored thereon, including plurality of industrial application programs running an engineering project involving multiple different disciplines, and a package manager client. The package manager client communicates with a remote repository server that hosts application packages, and sends requests for packages and receives package deliveries. The package manager client unbundles package metainformation relevant to a domain specific application and according to an industrial package information schema. A dependency tracking module identifies dependencies of a current package to other packages and generates a dependency tree that includes the name and version of each dependent package. An upgrade analyzer compares dependency trees to identify dependency incompatibilities as conflicting packages based on inconsistencies and performs an automated resolution of the dependency incompatibilities.
1. A system for industrial application package management, comprising:
a computing device comprising a processor and a memory having executable programs and applications stored thereon, comprising:
a plurality of software application programs running an engineering project involving multiple different disciplines, the project using packages of software data, the packages having interdependencies;
a package manager client, configured to:
communicate with a plurality of remote repository servers hosting industrial application packages, wherein the package manager client sends requests for industrial application packages and receives deliveries of industrial application packages, wherein each of the industrial application packages is versioned and bundled according to an industrial package information schema, and
unbundle the industrial application packages to retrieve package data including package meta-information relevant to each industrial application package and to a domain specific application;
the package manager client comprising a dependency tracking module configured to:
identify package dependencies of a first version of a first industrial application package and of an update version of the first industrial application package, and
generate a first dependency tree for the first version and a second dependency tree for the update version of the first industrial application package including the name and version of each industrial application package of the identified package dependencies; and
an upgrade analyzer configured to:
compare the first dependency tree and the second dependency tree to identify dependency incompatibilities as conflicting packages based on inconsistencies; and
perform an automated resolution of the dependency incompatibilities.
2. The system of claim 1 , wherein the automated resolution performed by the upgrade analyzer comprises:
executing a first attempt for resolution by upgrading the conflicting packages to later versions that are known to be compatible;
on a condition that there are remaining unresolved conflicting packages, executing a second attempt for resolution by downgrading more advanced versions of industrial application packages to achieve a degree of compatibility within a specified range; and
on a condition that there are remaining unresolved conflicting packages, executing a third attempt for resolution by upgrading industrial application packages to new versions with unknown compatibility and performing a test compile to determine potential compatibility.
3. The system of claim 1 , further comprising:
a security vulnerability analyzer configured to investigate each package version used in the dependency tree of a package and to track identified vulnerabilities with respect to downloaded packages.
4. The system of claim 1 , wherein the plurality of software application programs includes an engineering software, wherein the package manager client is integrated with the engineering software allowing the user to operate the engineering software while the package manager client operates in the background to identify packages compatible with target hardware being designed by the engineering software.
5. The system of claim 1 , wherein the meta-information includes samples of interfacing and usage information.
6. The system of claim 1 , wherein the meta-information includes binaries for different target systems.
7. The system of claim 1 , wherein the meta-information includes hardware compatibility information.
8. The system of claim 1 , wherein the meta-information includes package dependencies.
9. The system of claim 1 , wherein the meta-information includes package provider information.
10. The system of claim 1 , wherein the meta-information includes engineering software compatibility information.
11. The system of claim 1 , wherein the meta-information includes engineering software data add-on and integration information.
12. The system of claim 1 , wherein the meta-information includes custom attachment information.
13. The system of claim 1 , wherein the meta-information includes test program information.
14. The system of claim 1 , wherein the meta-information includes domain specific software source code.
15. The system of claim 1 , wherein the meta-information includes performance specifications/limitations.
16. The system of claim 1 , wherein the meta-information includes hardware recommendations.
17. The system of claim 1 , wherein the meta-information includes documentation of a package's contents.
18. The system of claim 1 , wherein the meta-information includes vendor information about package related services.
19. The system of claim 1 , wherein the meta-information includes known information technology (IT) security vulnerabilities.
20. The system of claim 1 , further comprising:
a bundling tool configured to bundle packages authored by a user, the packages bundled in accordance with the industrial package information schema.