CN106371838B - A kind of method and system for safeguarding software package dependency relationship - Google Patents
A kind of method and system for safeguarding software package dependency relationship Download PDFInfo
- Publication number
- CN106371838B CN106371838B CN201610784423.6A CN201610784423A CN106371838B CN 106371838 B CN106371838 B CN 106371838B CN 201610784423 A CN201610784423 A CN 201610784423A CN 106371838 B CN106371838 B CN 106371838B
- Authority
- CN
- China
- Prior art keywords
- software package
- version number
- interface
- dependence
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The present invention relates to software package maintenance area more particularly to a kind of method and system for safeguarding software package dependency relationship.The present invention passes through program library needed for parsing target program;For the interface assignment version number in described program library;Obtain the software package informatin that the interface relies on;Be associated with the interface version number and the software package informatin, formed dependence;The version number of interface needed for obtaining target program, obtains first version number;Dependence corresponding with the first version number is added to dependent file.By the information for the software package that the interface safeguarded in target program automatically is relied on, realization can obtain the software package that target program is relied on automatically.
Description
Technical field
The present invention relates to software package maintenance area more particularly to a kind of method and system for safeguarding software package dependency relationship.
Background technique
With the development in domestic e-payment market and payment technology, the software systems of payment terminal are also increasingly complicated.Mesh
Preceding payment terminal all employs greatly based on Linux even the complex operations system of Android, and supports to include IC card, magnetic
The a variety of peripheral hardwares driving such as card, radio-frequency card, various communication modes, and realize GUI, device service, management and apply etc. more more
Kind software function.These functions are due to being related to different developing departments, and upgrading frequency is also different, so being difficult to be managed collectively.It is based on
Related a kind of software is usually made into software module unified management by this characteristic.Such as: printing driving, IC card driving etc..It is common
The mode of maintenance software module be made as software package, such as: ipkg format software packet.These software packages by version information into
Row maintenance.It thereby realizes and is safeguarded as unit of software package.There are this certain dependence, institutes between software package
Software package dependency relationship is called, is exactly that only specific some software modules exist a software package at the terminal and version meets centainly
It is required that can just be installed in the terminal.By taking the dependence of the software package testapp of 1.3.1 version as an example: testsdk1 (>=
0.9), testsdk2 (>=1.3), testsdk3 (>=1.0).In this dependence, which needs to rely on three
Software package: testsdk1, testsdk2 and testsdk3.Three's release requirement is respectively: being not less than 0.9, is not less than 1.3, no
Lower than 1.0.The terminal for only meeting condition above could install the software package of 1.3.1 version.
Relatively common dependence is program in a software package or library has invoked the library in another software package.At present
Common methods are dependence of the hand filling software package to other software packet when generating software package.But hand filling is soft
The method of part packet dependence has the drawback that firstly, if program and library depend on the number in other libraries in a software package
Measure more, then dependence is easy to fail to fill in.Secondly, many libraries will increase interface newly with software upgrading, hand filling is error-prone.
Furthermore the application program in payment terminal is more difficult to control filling in for dependence by client development, application software package, can make
The problems such as at program is unable to operate normally.
Summary of the invention
The technical problems to be solved by the present invention are: a kind of method and system for safeguarding software package dependency relationship are provided, it is real
The associated software package of target program can be now obtained automatically.
In order to solve the above-mentioned technical problem, the technical solution adopted by the present invention are as follows:
The present invention provides a kind of method for safeguarding software package dependency relationship, comprising:
Program library needed for parsing target program;
For the interface assignment version number in described program library;
Obtain the software package informatin that the interface relies on;
Be associated with the interface version number and the software package informatin, formed dependence;
The version number of interface needed for obtaining target program, obtains first version number;
Dependence corresponding with the first version number is added to dependent file.
The present invention also provides a kind of systems for safeguarding software package dependency relationship, comprising:
Parsing module, for program library needed for parsing target program;
First distribution module, for for the interface assignment version number in described program library;
First obtains module, the software package informatin relied on for obtaining the interface;
First relating module, for be associated with the interface version number and the software package informatin, formed dependence;
Second acquisition module obtains first version number for obtaining the version number of interface needed for target program;
First adding module, for adding dependence corresponding with the first version number to dependent file.
The beneficial effects of the present invention are: by being conducive to in program library for the interface assignment version number in program library
Interface be managed collectively;Pass through the letter for the software package that the version number of the interface in associated program library and the interface rely on
Breath, is conducive to the dependence of the interface and other software packages in maintenance library;Pass through aggregation and interface needed for target program
Corresponding dependence forms dependent file, is conducive to know the software that target program is relied on by the dependent file
The information of packet;Realization can obtain automatically the software package that target program is relied on according to dependent file.
Detailed description of the invention
Fig. 1 is a kind of flow diagram for the method for safeguarding software package dependency relationship of the present invention;
Fig. 2 is a kind of structural block diagram for the system for safeguarding software package dependency relationship of the present invention;
Label declaration:
1, parsing module;2, the first distribution module;3, first module is obtained;4, the first relating module;5, second mould is obtained
Block;6, the first adding module;7, third obtains module;8, the 4th module is obtained;9, the second relating module;10, the second addition mould
Block;11, package module;12, module is increased newly;13, the second distribution module;14, the 5th module is obtained;15, third relating module;
16, third adding module;17, update module.
Specific embodiment
To explain the technical content, the achieved purpose and the effect of the present invention in detail, below in conjunction with embodiment and cooperate attached
Figure is explained.
The most critical design of the present invention is: the letter of the software package relied on by the interface in maintenance target program automatically
Breath, realization can obtain the software package that target program is relied on automatically.
As shown in Figure 1, the present invention provides a kind of method for safeguarding software package dependency relationship, comprising:
Program library needed for parsing target program;
For the interface assignment version number in described program library;
Obtain the software package informatin that the interface relies on;
Be associated with the interface version number and the software package informatin, formed dependence;
The version number of interface needed for obtaining target program, obtains first version number;
Dependence corresponding with the first version number is added to dependent file.
It further, is the interface assignment version number in described program library, specifically:
To have the identical version number of interface assignment of identical dependence in described program library.
Seen from the above description, unified management can be carried out to the interface with identical dependence, when target program institute
When the program library needed is more, be conducive to safeguard the software package informatin that target program relies on.
Further, the software package informatin, including software package title and software package version number.
Seen from the above description, the dependence of interface can be specified by software package title and software package version number.
Generally, there are this certain dependence between software package, so-called software package dependency relationship is exactly one soft
Only specific some software modules exist part packet at the terminal and version meets certain requirements can just be installed in the terminal.Therefore
When the dependence of the interface needed for describing target program, it should illustrate the version number of relied on software package title and its requirement.
Further, the software package version number is the software package that the interface in described program library can be supported to operate normally
Minimum version number.
Seen from the above description, software package can be usually compatible with forward, i.e., the software package of more highest version includes compared with lowest version
Institute is functional, thus the minimum version number of the software package relied on by interface would know that can supporting interface operate normally it is all
The version number of software package.
Further, further includes:
The software package version number in dependent file with same software packet title is obtained, software package version number set is formed;
Highest software package version number in software package version number set is obtained, optimal version number is obtained;
It is associated with the software package title and the optimal version number, forms optimal dependence;
The optimal dependence is added to the dependent file.
Seen from the above description, the quantity for obtaining the software package that target program relies on can be reduced by realizing.Dependent file description
Be the software package that total interface is relied in target program information, it is understood that there may be some interfaces rely on software package it is identical but
The different situation of software package version number then need to only be obtained in dependent file and be wanted with highest since software package can be usually compatible with forward
The corresponding software package of version number is sought, the demand of all interfaces for relying on same software package can be met.
Further, further includes:
It encapsulates the target program and dependent file is target software packet.
Seen from the above description, target software packet dependence according to described in dependent file obtains target journey automatically
The software package that sequence relies on.
Further, further includes:
It is newly-increased to be interfaced to described program library;
For the newly-increased interface assignment version number;
Obtain the software package informatin that the newly-increased interface relies on;
The version number and the software package informatin, formation for being associated with the newly-increased interface increase dependence newly;
The newly-increased dependence is added to the dependent file;
Update the dependent file in the target software packet.
Seen from the above description, when the program library of target program increases interface newly, automatically by the dependence of newly-increased interface
It is updated to dependent file.
As shown in Fig. 2, the present invention also provides a kind of systems for safeguarding software package dependency relationship, comprising:
Parsing module 1, for program library needed for parsing target program;
First distribution module 2, for for the interface assignment version number in described program library;
First obtains module 3, the software package informatin relied on for obtaining the interface;
First relating module 4, for be associated with the interface version number and the software package informatin, formed dependence;
Second acquisition module 5 obtains first version number for obtaining the version number of interface needed for target program;
First adding module 6, for adding dependence corresponding with the first version number to dependent file.
Further, further includes:
Third obtains module 7, for obtaining the software package version number in dependent file with same software packet title, is formed
Software package version number set;
4th obtains module 8, for obtaining highest software package version number in software package version number set, obtains optimal version
This number;
Second relating module 9 forms optimal dependence and closes for being associated with the software package title and the optimal version number
System;
Second adding module 10, for adding the optimal dependence to the dependent file;
Package module 11, for encapsulating the target program and dependent file as target software packet.
Further, further includes:
Newly-increased module 12 is interfaced to described program library for newly-increased;
Second distribution module 13, for being the newly-increased interface assignment version number;
5th obtains module 14, the software package informatin relied on for obtaining the newly-increased interface;
Third relating module 15, the version number and the software package informatin, formation for being associated with the newly-increased interface are newly-increased
Dependence;
Third adding module 16, for adding the newly-increased dependence to the dependent file;
Update module 17, for updating the dependent file in the target software packet.
The embodiment of the present invention one are as follows:
Program library needed for parsing target program;
To have the identical version number of interface assignment of identical dependence in described program library;
Obtain title and the version number of the software package that the interface relies on;The version number is that can support in described program library
Interface operate normally software package minimum version number;
Be associated with the interface version number and the software package informatin, formed dependence;
The version number of interface needed for obtaining target program, obtains first version number;
Dependence corresponding with the first version number is added to dependent file;
It encapsulates the target program and dependent file is target software packet.
Seen from the above description, the present embodiment can obtain automatically target program institute by the dependent file in target software packet
The software package of dependence.
The application scenarios of the present embodiment are as follows:
By readelf command analysis target program testapp, program library used in target program is obtained
libtestsdk1.so;
It include interface func1, interface func2 and interface func3 in program library libtestsdk1.so, due to above-mentioned interface
Dependence having the same, therefore identical version number TESTSDK1_1.0 is distributed for them;
The information of associated version TESTSDK1_1.0 and the software package of dependence, specifically:
[LibName]
Name=libtestsdk1.so
[Depends]
TESTSDK1_1.0=testsdk1 (>=1.0);Wherein, Name indicates corresponding program library file title,
[Depends] describes each interface version in library to the dependence of some software packages, the usually software package where the library,
Software package release requirement in the special interface version in library.;
Library libtestsdk1.so is located in software package testsdk1, so literary style above shows: if application program
Or application library has invoked the function (such as func2) for belonging to interface version " TESTSDK1_1.0 " in libtestsdk1.so, that
, the application program or application library depend on software package testsdk1, and the software package version must be equal to greatly 1.0.
The version number of interface func1 needed for obtaining target program testapp, obtains first version TESTSDK1_1.0;
Dependence corresponding with the first version TESTSDK1_1.0 is added to dependent file;
It encapsulates the target program and dependent file is target software packet.
The embodiment of the present invention two are as follows:
On the basis of example 1, it increases newly and is interfaced to described program library;
For the newly-increased interface assignment version number;
Obtain the software package informatin that the newly-increased interface relies on;
The version number and the software package informatin, formation for being associated with the newly-increased interface increase dependence newly;
The newly-increased dependence is added to the dependent file;
Update the dependent file in the target software packet.
Seen from the above description, dependent file is safeguarded automatically when the present embodiment realizes newly-increased interface.
The application scenarios of the present embodiment are as follows: newly-increased interface func4 distributes version number TESTSDK1_1.1 for it.Acquisition connects
The software package informatin that mouthful func4 is relied on is testsdk1 (>=1.1).The dependence of newly-increased interface func4 is added to dependence
File.
The embodiment of the present invention three are as follows:
On the basis of example 1, the present embodiment:
The software package version number in dependent file with same software packet title is obtained, software package version number set is formed;
Highest software package version number in software package version number set is obtained, optimal version number is obtained;
It is associated with the software package title and the optimal version number, forms optimal dependence;
The optimal dependence is added to the dependent file.
Seen from the above description, the present embodiment realizes the quantity for reducing and obtaining the software package that target program relies on.
For each library used, optimal dependence is generated.Such as: target program has used interface func4 and has connect
Mouth func1, then the highest interface version of library libtestsdk1.so is TESTSDK1_1.1.In the library of all system libraries of SDK
In dependent file, to each library that testapp is used, corresponding dependence is found according to highest interface version.It is connect according to highest
The dependence of mouth version obtains corresponding software package.
The embodiment of the present invention four are as follows:
Program library needed for parsing module 1 parses target program;
First distribution module 2 is the interface assignment version number in described program library;
First acquisition module 3 obtains the software package informatin that the interface relies on;
First relating module 4 be associated with the interface version number and the software package informatin, formed dependence;
Second obtains the version number of interface needed for module 5 obtains target program, obtains first version number;
First adding module 6 adds dependence corresponding with the first version number to dependent file;
Third obtains module 7 and obtains the software package version number in dependent file with same software packet title, forms software
Wrap version number's set;
4th, which obtains module 8, obtains highest software package version number in software package version number set, obtains optimal version number;
Second relating module 9 is associated with the software package title and the optimal version number, forms optimal dependence;
Second adding module 10 adds the optimal dependence to the dependent file;
Newly-increased module 12 is newly-increased to be interfaced to described program library;
Second distribution module 13 is the newly-increased interface assignment version number;
5th acquisition module 14 obtains the software package informatin that the newly-increased interface relies on;
Third relating module 15 is associated with the version number of the newly-increased interface and the software package informatin, newly-increased rely on of formation are closed
System;
Third adding module 16 adds the newly-increased dependence to the dependent file;
Update module 17 updates the dependent file in the target software packet;
Package module 11 encapsulates the target program and dependent file is target software packet.
In conclusion a kind of method and system for safeguarding software package dependency relationship provided by the invention, by for program library
In interface assignment version number, be conducive to be managed collectively the interface in program library;Pass through the interface in associated program library
Version number and the information of software package that relies on of the interface, be conducive to interface in maintenance library and other software packages according to
The relationship of relying;By assembling dependence corresponding with interface needed for target program, dependent file is formed, is conducive to by described
Dependent file knows the information for the software package that target program is relied on;Realization can obtain automatically target program institute according to dependent file
The software package of dependence;Further, unified management can be carried out to the interface with identical dependence, needed for target program
Program library it is more when, be conducive to safeguard target program rely on software package informatin;Further, by software package title and soft
The dependence of interface can be specified in Jian Bao version number;Further, software package can be usually compatible with forward, i.e. the software of more highest version
Packet is functional comprising the institute compared with lowest version, therefore the minimum version number of the software package relied on by interface would know that and can support to connect
The version number for all software packages that mouth operates normally;Further, the software package for obtaining that target program relies on can be reduced by realizing
Quantity;Further, further includes: target software packet can the dependence according to described in dependent file obtain target program automatically
The software package of dependence;Further, when the program library of target program increases interface newly, automatically more by the dependence of newly-increased interface
Newly to dependent file.
The above description is only an embodiment of the present invention, is not intended to limit the scope of the invention, all to utilize this hair
Equivalents made by bright specification and accompanying drawing content are applied directly or indirectly in relevant technical field, similarly include
In scope of patent protection of the invention.
Claims (10)
1. a kind of method for safeguarding software package dependency relationship characterized by comprising
Program library needed for parsing target program;
For the interface assignment version number in described program library;
Obtain the software package informatin that the interface relies on;
Be associated with the interface version number and the software package informatin, formed dependence;
The version number of interface needed for obtaining target program, obtains first version number;
Dependence corresponding with the first version number is added to dependent file.
2. a kind of method for safeguarding software package dependency relationship according to claim 1, which is characterized in that be described program library
In interface assignment version number, specifically:
To have the identical version number of interface assignment of identical dependence in described program library.
3. a kind of method for safeguarding software package dependency relationship according to claim 1, which is characterized in that the software package letter
Breath, including software package title and software package version number.
4. a kind of method for safeguarding software package dependency relationship according to claim 3, which is characterized in that the software package version
This number be the software package that the interface in described program library can be supported to operate normally minimum version number.
5. a kind of method for safeguarding software package dependency relationship according to claim 4, which is characterized in that further include:
The software package version number in dependent file with same software packet title is obtained, software package version number set is formed;
Highest software package version number in software package version number set is obtained, optimal version number is obtained;
It is associated with the software package title and the optimal version number, forms optimal dependence;
The optimal dependence is added to the dependent file.
6. a kind of method for safeguarding software package dependency relationship according to claim 1, which is characterized in that further include:
It encapsulates the target program and dependent file is target software packet.
7. a kind of method for safeguarding software package dependency relationship according to claim 6, which is characterized in that further include:
It is newly-increased to be interfaced to described program library;
For the newly-increased interface assignment version number;
Obtain the software package informatin that the newly-increased interface relies on;
The version number and the software package informatin, formation for being associated with the newly-increased interface increase dependence newly;
The newly-increased dependence is added to the dependent file;
Update the dependent file in the target software packet.
8. a kind of system for safeguarding software package dependency relationship characterized by comprising
Parsing module, for program library needed for parsing target program;
First distribution module, for for the interface assignment version number in described program library;
First obtains module, the software package informatin relied on for obtaining the interface;
First relating module, for be associated with the interface version number and the software package informatin, formed dependence;
Second acquisition module obtains first version number for obtaining the version number of interface needed for target program;
First adding module, for adding dependence corresponding with the first version number to dependent file.
9. a kind of system for safeguarding software package dependency relationship according to claim 8, which is characterized in that further include:
Third obtains module, for obtaining the software package version number in dependent file with same software packet title, forms software
Wrap version number's set;
4th obtains module, for obtaining highest software package version number in software package version number set, obtains optimal version number;
Second relating module forms optimal dependence for being associated with the software package title and the optimal version number;
Second adding module, for adding the optimal dependence to the dependent file;
Package module, for encapsulating the target program and dependent file as target software packet.
10. a kind of system for safeguarding software package dependency relationship according to claim 9, which is characterized in that further include:
Newly-increased module is interfaced to described program library for newly-increased;
Second distribution module, for being the newly-increased interface assignment version number;
5th obtains module, the software package informatin relied on for obtaining the newly-increased interface;
Third relating module, version number and the software package informatin, newly-increased rely on of formation for being associated with the newly-increased interface close
System;
Third adding module, for adding the newly-increased dependence to the dependent file;
Update module, for updating the dependent file in the target software packet.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610784423.6A CN106371838B (en) | 2016-08-31 | 2016-08-31 | A kind of method and system for safeguarding software package dependency relationship |
PCT/CN2017/097826 WO2018040926A1 (en) | 2016-08-31 | 2017-08-17 | Method and system for maintaining software package dependency |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610784423.6A CN106371838B (en) | 2016-08-31 | 2016-08-31 | A kind of method and system for safeguarding software package dependency relationship |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106371838A CN106371838A (en) | 2017-02-01 |
CN106371838B true CN106371838B (en) | 2019-10-18 |
Family
ID=57899421
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201610784423.6A Active CN106371838B (en) | 2016-08-31 | 2016-08-31 | A kind of method and system for safeguarding software package dependency relationship |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN106371838B (en) |
WO (1) | WO2018040926A1 (en) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106371838B (en) * | 2016-08-31 | 2019-10-18 | 福建联迪商用设备有限公司 | A kind of method and system for safeguarding software package dependency relationship |
CN107193616A (en) * | 2017-06-30 | 2017-09-22 | 广州云移信息科技有限公司 | A kind of application program updating method and terminal |
CN107678776A (en) * | 2017-08-09 | 2018-02-09 | 上海壹账通金融科技有限公司 | Multimode version dependence construction method, device, server and storage medium |
CN108334334B (en) * | 2018-03-07 | 2022-02-01 | 政采云有限公司 | Method and system for managing dependent package version |
CN108965295B (en) * | 2018-07-17 | 2021-09-17 | 郑州云海信息技术有限公司 | File compression and combination method and related device |
CN109002314A (en) * | 2018-09-29 | 2018-12-14 | 深圳市元征科技股份有限公司 | Oftware updating method, device, electronic equipment and storage medium |
CN111124526A (en) * | 2018-11-01 | 2020-05-08 | 北京奇虎科技有限公司 | Dependency management method, dependency management device, storage medium and computer equipment |
CN111258620B (en) * | 2018-11-30 | 2022-02-22 | 中兴通讯股份有限公司 | Method, device and equipment for generating differential upgrade package |
CN110008039B (en) * | 2019-03-07 | 2020-11-03 | 平安国际智慧城市科技股份有限公司 | Interface control method, device, computer readable storage medium and computer equipment |
CN110377514A (en) * | 2019-07-12 | 2019-10-25 | 中汇信息技术(上海)有限公司 | Management method, device, electronic equipment and the storage medium of software component |
CN110737460A (en) * | 2019-09-04 | 2020-01-31 | 厦门网宿有限公司 | platform project management method and device |
CN110990051B (en) * | 2019-11-27 | 2023-07-21 | 锐捷网络股份有限公司 | Maintenance method, device, medium and equipment for software package dependency relationship |
CN112214408A (en) * | 2020-10-12 | 2021-01-12 | 北京字节跳动网络技术有限公司 | Dependency conflict detection method and device, electronic equipment and computer readable medium |
CN112540775A (en) * | 2020-12-21 | 2021-03-23 | 恩亿科(北京)数据科技有限公司 | Method, device and equipment for detecting compatibility of program package |
CN115469916B (en) * | 2022-08-19 | 2023-06-20 | 武汉烽火技术服务有限公司 | Implementation method, system and device of southbound interface compatible with multiple versions |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101233485A (en) * | 2005-06-02 | 2008-07-30 | 数学工程公司 | Calling of late bound functions from an external program environment |
CN102945155A (en) * | 2012-10-22 | 2013-02-27 | 中标软件有限公司 | Linux operation system software package and dependency deficiency detecting method thereof |
CN103119561A (en) * | 2010-09-23 | 2013-05-22 | 苹果公司 | Systems and methods for compiler-based vectorization of non-leaf code |
CN103425512A (en) * | 2013-08-19 | 2013-12-04 | 曙光信息产业股份有限公司 | Software package management method and system |
CN104850401A (en) * | 2015-05-07 | 2015-08-19 | 南京大学 | Method for replacing Hadoop storage module by using PVFS (Parallel Virtual File System) |
US9430200B1 (en) * | 2015-06-04 | 2016-08-30 | Microsoft Technology Licensing Llc | Cross-library framework architecture feature sets |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3698021B2 (en) * | 2000-06-12 | 2005-09-21 | 日本電気株式会社 | Wide area distributed asset version management system, wide area distributed asset version management method, recording medium |
CN106371838B (en) * | 2016-08-31 | 2019-10-18 | 福建联迪商用设备有限公司 | A kind of method and system for safeguarding software package dependency relationship |
-
2016
- 2016-08-31 CN CN201610784423.6A patent/CN106371838B/en active Active
-
2017
- 2017-08-17 WO PCT/CN2017/097826 patent/WO2018040926A1/en active Application Filing
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101233485A (en) * | 2005-06-02 | 2008-07-30 | 数学工程公司 | Calling of late bound functions from an external program environment |
CN103119561A (en) * | 2010-09-23 | 2013-05-22 | 苹果公司 | Systems and methods for compiler-based vectorization of non-leaf code |
CN102945155A (en) * | 2012-10-22 | 2013-02-27 | 中标软件有限公司 | Linux operation system software package and dependency deficiency detecting method thereof |
CN103425512A (en) * | 2013-08-19 | 2013-12-04 | 曙光信息产业股份有限公司 | Software package management method and system |
CN104850401A (en) * | 2015-05-07 | 2015-08-19 | 南京大学 | Method for replacing Hadoop storage module by using PVFS (Parallel Virtual File System) |
US9430200B1 (en) * | 2015-06-04 | 2016-08-30 | Microsoft Technology Licensing Llc | Cross-library framework architecture feature sets |
Also Published As
Publication number | Publication date |
---|---|
CN106371838A (en) | 2017-02-01 |
WO2018040926A1 (en) | 2018-03-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106371838B (en) | A kind of method and system for safeguarding software package dependency relationship | |
US20190102157A1 (en) | Optimizing redeployment of functions and services across multiple container platforms and installations | |
US9043458B2 (en) | Framework for facilitating implementation of multi-tenant SaaS architecture | |
US7302462B2 (en) | Framework and methods for dynamic execution of digital data processor resources | |
US20180131514A1 (en) | Dynamic licensing for applications and plugin framework for virtual network systems | |
US20020069399A1 (en) | System of reusable software parts and methods of use | |
CN110032392A (en) | Service administering method and device, storage medium and electronic equipment | |
CN108984160A (en) | Information-based Quick Development Framework and method based on modularization | |
CN107329762B (en) | Method and system for describing and integrating software service | |
US20130145381A1 (en) | Web api server program, web api publication method | |
CN114328509A (en) | Service processing method and device | |
US7996500B2 (en) | Systems and methods for extensible distributed configuration management | |
CN109240733A (en) | A kind of method and terminal updating advertisement SDK based on Android system | |
US9110758B2 (en) | Cross-platform software framework for embedded systems on data storage device | |
CN1384440A (en) | Control system | |
CN115033230A (en) | Method, device, equipment and medium for generating driver of embedded hardware platform | |
US9588947B1 (en) | Integrated administrative interface for open network programming applications | |
CN105122209A (en) | Web services provided from software framework | |
CN104918113B (en) | A kind of the function card end compatibility method and system of module TV | |
US20220326939A1 (en) | Mobile service upgrade method and apparatus, and terminal | |
KR101943936B1 (en) | Integrated external interconnection system and method for web standard application development | |
US20100023948A1 (en) | Allocating resources in a multicore environment | |
CN109324838A (en) | Execution method, executive device and the terminal of SCM program | |
CN115167985A (en) | Virtualized computing power providing method and system | |
CN114237634A (en) | Application release risk identification method, device, equipment, medium and program product |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |