CN104881311A - Method and apparatus for judging version compatibility - Google Patents
Method and apparatus for judging version compatibility Download PDFInfo
- Publication number
- CN104881311A CN104881311A CN201510283911.4A CN201510283911A CN104881311A CN 104881311 A CN104881311 A CN 104881311A CN 201510283911 A CN201510283911 A CN 201510283911A CN 104881311 A CN104881311 A CN 104881311A
- Authority
- CN
- China
- Prior art keywords
- component software
- version
- edition
- compatibility
- component
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000004590 computer program Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000010354 integration Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a method for judging version compatibility, which comprises the steps: acquiring an integrated configuration file of a software component system, wherein the integrated configuration file comprises configuration information of N software components when the software component system is upgraded, N software components comprise at least one upgraded software component and N is greater than or equal to 1; acquiring version description files of the N software components; judging whether a random version of each software component is compatible according to the version description file of each of the N software components, and determining to carry out stable upgrading of the software component system. The embodiment of the invention also discloses an apparatus for judging version compatibility.
Description
Technical field
The present invention relates to the embedded software Component-Based Development Techniques in computer realm, particularly relate to a kind of determination methods and device of edition compatibility.
Background technology
In general hardware and software platform software life-cycle, software towards application very complicated and changeable, therefore, need to upgrade accordingly renewal to software version timely, to adapt to software defect reparation, the demand such as software function strengthens, software performance optimization and software runtime environment change.
In prior art, adopt the software development that Component-based Design method is carried out.Wherein, a software is made up of multiple component software, each component software has oneself version, such as, the component software of embedded software and upper computer software can comprise three classes: source code assembly (during compiling assembly), binary code assembly (during link assembly), executable code assembly (during operation assembly).When there being the redaction integration release of certain component software in software, component software system is upgraded separately to this component software again or all component softwares of component software system to this software are upgraded, to complete the upgrading to this component software.
But, at hardware and software platform, modularization, under the development mode of modularization framework, when adopting the upgrading mode of the component software of prior art, individual software assembly can be upgraded separately, but when individual software assembly cross-version is upgraded, after the component software upgrading of redaction may be run into, incompatible problem is there is with the component software that in component software system, other need not be upgraded, the component software system of the component software and other component software that need not upgrade comprising above-mentioned redaction can not normally be run, thus cause the instability of component software system.Therefore, when individual software assembly can be upgraded separately, the judgement of the compatibility in component software system between component software becomes the key solved the problem.
Summary of the invention
For solving the problems of the technologies described above, the embodiment of the present invention expects the determination methods and the device that provide a kind of edition compatibility, can judge the edition compatibility between component software, ensures the stability of component software system upgrade.
Technical scheme of the present invention is achieved in that
The embodiment of the present invention provides a kind of determination methods of edition compatibility, and described method comprises:
Obtain the integrated configuration file of component software system, described integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, and described N number of component software comprises the component software of at least one upgrading, wherein, and N >=1;
Obtain the Version Description file of described N number of component software;
According to the Version Description file of each component software in described N number of component software, judge that whether any version of described each component software is compatible, determine the stable upgrading carrying out described component software system.
In such scheme, the Version Description file of described each component software comprises: the dependence between other N-1 component software in each component software and described N number of component software except self;
Accordingly, the described Version Description file according to each component software in described N number of component software, judges that whether any version of described each component software is compatible, comprising:
According to the dependence between each component software and described other N-1 component software, determine that described each component software is by the version relied on;
Judge that whether described each component software is compatible by the version relied on.
In such scheme, the Version Description file of any one component software in described N number of component software also comprises: the compatibility of the current version information of any one component software described, the previous release information of any one component software described, the current version information of any one component software described and the previous release information of any one component software described marks, and the old version information of any one component software described;
Accordingly, judge that any one component software described is by the whether compatible method of the version that relies on, comprising:
Compatibility according to the previous release information of the previous release information of the current version information of any one component software described, any one component software described, the current version information of any one component software described and any one component software described marks, and the old version information of any one component software described, the edition tree between any version of any one component software described in generating;
According to the edition tree between any version of any one component software described, judge that whether any one component software described is compatible by the version relied on.
In such scheme, the edition tree between any version of any one component software described in described basis, judges that whether any one component software described is compatible by the version relied on, comprising:
In edition tree between any version of any one component software described, judge any one component software described by any two versions of relying on are in compatible branch time, any one component software described is by any two edition compatibilities relied on.
In such scheme, any one component software described is by after any two edition compatibilities of relying on, and described method also comprises:
Described each component software in described N number of component software by rely on any two edition compatibilities time, determine the edition compatibility of described component software system.
The embodiment of the present invention provides a kind of judgment means of edition compatibility, and described device comprises:
Acquiring unit, for obtaining the integrated configuration file of component software system, described integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, and described N number of component software comprises the component software of at least one upgrading, wherein, N >=1;
Described acquiring unit, also for obtaining the Version Description file of described N number of component software;
Judging unit, for the Version Description file of each component software in described N number of component software of obtaining according to described acquiring unit, judges that whether any version of described each component software is compatible, determines the stable upgrading carrying out described component software system.
In such scheme, the Version Description file of described each component software that described acquiring unit obtains comprises: the dependence between other N-1 component software in each component software and described N number of component software except self; The judgment means of described edition compatibility, also comprises: determining unit;
Described determining unit, for the dependence between each component software of obtaining according to described acquiring unit and described other N-1 component software, determines that described each component software is by the version relied on;
Described judging unit, whether compatible by the version relied on specifically for judging described each component software that described determining unit is determined.
In such scheme, the Version Description file of any one component software in described N number of component software that described acquiring unit obtains also comprises: the compatibility of the current version information of any one component software described, the previous release information of any one component software described, the current version information of any one component software described and the previous release information of any one component software described marks, and the old version information of any one component software described; The judgment means of described edition compatibility also comprises: generation unit;
Generation unit, compatibility for the previous release information of the current version information of any one component software described in obtaining according to described acquiring unit, the previous release information of any one component software described, the current version information of any one component software described and any one component software described marks, and the old version information of any one component software described, the edition tree between any version of any one component software described in generating;
Described judging unit, also specifically for any one component software described in generating according to described generation unit any version between edition tree, judge that whether any one component software described that described determining unit is determined compatible by the version relied on.
In such scheme, judging unit, also specifically for any one component software described in generating at described generation unit any version between edition tree in, any one component software described by any two versions of relying on are in compatible branch time, any one component software described is by any two edition compatibilities relied on.
In such scheme, described determining unit, also judge that any one component software described is by after any two edition compatibilities of relying on for described judging unit, described judging unit judge described each component software in described N number of component software by rely on any two edition compatibilities time, determine the edition compatibility of described component software system.
Embodiments provide a kind of determination methods and device of edition compatibility, the judgment means of edition compatibility obtains the integrated configuration file of component software system, integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, and N number of component software comprises the component software of at least one upgrading; Obtain the Version Description file of N number of component software; According to the Version Description file of component software each in N number of component software, judge that whether any version of each component software is compatible, to determine the stable upgrading carrying out component software system.Adopt above-mentioned technic relization scheme, when judgment means due to edition compatibility has the component software of redaction to upgrade in component software system, first judge that whether any version of each component software in component software system is compatible, and then judge that whether each component software is compatible by the version relied on, thus can determine that whether the version of these software systems when using the component software of upgrading be compatible, therefore, compatibility determination is completed by the judgment means of edition compatibility, component software system can be made when edition compatibility to carry out the edition upgrading of single component software, thus ensure that the stability of component software system upgrade.
Accompanying drawing explanation
The process flow diagram one of the determination methods of a kind of edition compatibility that Fig. 1 provides for the embodiment of the present invention;
The flowchart 2 of the determination methods of a kind of edition compatibility that Fig. 2 provides for the embodiment of the present invention;
The version dependence graph of the exemplary component software that Fig. 3 provides for the embodiment of the present invention;
The flow chart 3 of the determination methods of a kind of edition compatibility that Fig. 4 provides for the embodiment of the present invention;
The edition tree of the exemplary single component software that Fig. 5 provides for the embodiment of the present invention;
The version dependence graph of the exemplary component software that Fig. 6 provides for the embodiment of the present invention is to the evolution of the edition tree of each single component software;
The process flow diagram four of the determination methods of a kind of edition compatibility that Fig. 7 provides for the embodiment of the present invention;
The structural representation one of the judgment means of a kind of edition compatibility that Fig. 8 provides for the embodiment of the present invention;
The structural representation two of the judgment means of a kind of edition compatibility that Fig. 9 provides for the embodiment of the present invention;
The structural representation three of the judgment means of a kind of edition compatibility that Figure 10 provides for the embodiment of the present invention;
The structural representation of a kind of computing machine that Figure 11 provides for the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described.
The executive agent of the embodiment of the present invention can for being arranged on the judgment means of the edition compatibility in computing machine or integration module that is external and computing machine, and the present invention is not restricted, and is arranged in computing machine is below described for the judgment means of edition compatibility.
Embodiment one
Embodiments of the invention provide a kind of determination methods of edition compatibility, and as shown in Figure 1, the method can comprise:
The integrated configuration file of S101, acquisition component software system, this integrated configuration file comprises the configuration information of N number of component software when component software system is upgraded, and this N number of component software comprises component software of at least one upgrading, wherein, N >=1.
The application scenarios of the embodiment of the present invention is: when having the component software of redaction to issue in certain component software system, and this component software system will be upgraded the situation of component software of this redaction; This step can be completed by the judgment means of edition compatibility.
It should be noted that, the integration release of a component software is undertaken by research staff; Concrete:
First, configure the Version Description file of this component software, specifically can fill in the version information of corresponding component software according to form; When component software is issued, synchronously provide component software Version Description file.The compatibility recording the previous release information of the current version information of this component software, the previous release information of this component software, the current version information of this component software and this component software in Version Description file marks, and retain record and the dependence of the old version information of this component software exploitation, here, dependence refers to that this component software relies on the dependence between other component software except self in component software system.When this component software relies on other component software, fill in the current version information of relied on component software.
Secondly, the integrated configuration file of configuration software component system, specifically fills in the integrated configuration file of component software system.Component software integrated needed for different application personnel, version may be different, therefore, by the integrated configuration file of component software system, describe the configuration information of this each component software included by component software system; Wherein, in integrated configuration file, configure N number of component software of this component software system.
Concrete, the configuration information of N number of component software that integrated configuration file comprises can be N number of software component names and each self-corresponding current version information thereof.
Optionally, the version information in the embodiment of the present invention can be version number.
It should be noted that, the current version information in the embodiment of the present invention refers to the current version that will use of component software, and previous release information refers to the legacy version information before current version upgrading.
In embodiments of the present invention, after often issuing the redaction of a component software, the judgment means of edition compatibility just therefrom can get the integrated configuration file of above-mentioned component software system, and from this integrated configuration file, obtain the configuration information of N number of component software required when this component software system is upgraded.
It should be noted that, the component software (component software of redaction) of at least one upgrading should be comprised in the N number of component software in component software system, be just necessary the judgement carrying out component software system compatible.
Exemplary, component software system can be made up of three component softwares, and the integrated configuration file of this component software system comprises the configuration information of the IEC103 of SLAVE and the V1.1 version of MASTER, V1.2 version of V1.3 version; Integrated configuration file example is as follows:
Key＝MASTER Version＝1.3 Time＝2014-12-06_16:29:59 Crc＝8F6DE121
Key＝SLAVE Version＝1.2 Time＝2014-11-11_20:27:19 Crc＝2E9F6B30
key＝IEC103 Version＝1.1 Time＝2014-10-22_10:25:36 Crc＝6A5BC31E
Wherein, Key represents the title of component software, and Version represents the version information of component software, and Time is component software compiling formation time, and CRC is the check code of component software.
S102, obtain the Version Description file of N number of component software.
This step can be completed by the judgment means of edition compatibility; It should be noted that, the judgment means of edition compatibility is after the N number of component software determining component software system, the judgment means of this edition compatibility only need judge the compatibling problem of this N number of component software, so, the judgment means of this edition compatibility obtains the Version Description file of N number of component software, to carry out the judgement of component software compatibility.
Optionally, the Version Description file of each component software in N number of component software comprises: the dependence between other N-1 component software in each component software and N number of component software except self.
Exemplary, the Version Description file of MASTER comprises: the MASTER of V1.3 relies on the SLAVE of V1.1; The Version Description file of SLAVE comprises: the SLAVE of V1.2 version relies on the MASTER of V1.3; The Version Description file of IEC103 comprises: the IEC103 of V1.2 relies on the MASTER of SLAVE and V1.2 of V1.0.
Optionally, the Version Description file of any one component software in N number of component software also comprises: the compatibility of the current version information of any one component software, the previous release information of any one component software, the current version information of any one component software and the previous release information of any one component software marks, and the old version information of any one component software.
It should be noted that, when single component software issues redaction, need the Version Description file of update software assembly, and retain the descriptor of old version.
Exemplary, the form of the Version Description file of any one component software of N number of component software can be following form:
Wherein, Key is the title of component software, and Current is the current version information of component software, and Child is child release (current version), Parent is father's version (previous release), and Compatible is compatible mark.DependKey is the title of other component software that component software relies on, and ReqV is the version information of other component software relied on.
S103, Version Description file according to each component software in N number of component software, judge that whether any version of this each component software is compatible, determine the stable upgrading carrying out component software system.
This step can be completed by the judgment means of edition compatibility; After the judgment means of edition compatibility obtains the Version Description file of N number of component software, the judgment means of this edition compatibility is by the Version Description file according to each component software in this N number of component software, judge that whether any version of this each component software is compatible, and then judge the version compatibility of the component software system be made up of N number of component software, thus determine the stability of this component software system upgrade.
Concrete, as shown in Figure 2, after the judgment means execution S101-S102 of edition compatibility, the judgment means of edition compatibility is according to the Version Description file of each component software in N number of component software, judge that whether any version of this each component software is compatible, can step be comprised: S1031 and S1032; Specific as follows:
The judgment means of S1031, edition compatibility, according to the dependence of each component software and other N-1 component software, determines that each component software is by the version relied on.
After the judgment means of edition compatibility obtains the Version Description file of N number of component software, due to the dependence between other N-1 component software that the Version Description file of each component software comprises in each component software and N number of component software except self, therefore, the judgment means of this edition compatibility according to the dependence between each component software and other N-1 component software, can determine that each component software is by the version relied on.
It should be noted that, the judgment means of edition compatibility according to the dependence between each component software and other N-1 component software, can be determined that each component software is by the version relied on, thus draws the version dependence graph of component software system.
Exemplary, the Version Description file of MASTER comprises: the MASTER of V1.3 relies on the SLAVE of V1.1; The Version Description file of SLAVE comprises: the SLAVE of V1.2 version relies on the MASTER of V1.3; The Version Description file of IEC103 comprises: the IEC103 of V1.2 relies on the MASTER of SLAVE and V1.2 of V1.0.The judgment means of edition compatibility can according to the Version Description file of the Version Description file of MASTER, SLAVE, and the Version Description file of IEC103, derives:
(1), MASTER by the version information that other assembly relies on is: V1.3, V1.2, and the current version information of MASTER is V1.3;
(2), SLAVE by the version information that other assembly relies on is: V1.1, V1.0, and the current version information of SLAVE is V1.2;
(3), IEC103 do not rely on by other assembly, and the current version information of IEC103 is V1.1.
Wherein, the version dependence graph of the component software of the example provided in the embodiment of the present invention is for shown in Fig. 3.
The judgment means of S1032, edition compatibility judges that whether each component software is compatible by the version relied on.
It should be noted that, in embodiments of the present invention, the version match of component software system is split as and judges that each component software is by the whether compatible problem of the version that relies on by the judgment means of edition compatibility.A component software system is made up of N number of component software, then whole software systems form at most N* (N-1)/2 dependence, form single component software successively by the version information relied on, if the version information compatibility of single component software, and can develop to the current version of this single component software, then carry out version merger, like this, the judgment means of edition compatibility can be judged as that this single component software meets the dependence requirement of other component software, in component software system, the version of this single component software is compatible, therefore, the criterion of the edition compatibility of the whole component software system of the embodiment of the present invention is: if each component software is all edition compatibility in component software system, then the version of whole component software system is compatible.
Concrete, the judgment means of edition compatibility determines that each component software is by after the version that relies on, owing to also comprising in the Version Description file of each component software: the current version information of each component software, the previous release information of each component software, the compatibility of the current version information of each component software and the previous release information of each component software marks, and the old version information of each component software, therefore, the judgment means of this edition compatibility can according to the information in the Version Description file of above-mentioned each component software, judge that whether each component software is compatible by the version relied on.
Concrete, as shown in Figure 4, the judgment means of edition compatibility judges that any one component software is by the whether compatible method of the version that relies on, comprises step: S10321-S10322; Specific as follows:
The judgment means of S10321, edition compatibility marks according to the compatibility of the previous release information of the current version information of any one component software, the previous release information of this any one component software, the current version information of this any one component software and this any one component software, and the old version information of this any one component software, the edition tree between any version generating this any one component software.
Concrete, the judgment means of edition compatibility determines that each component software is by after the version that relies on, first the judgment means of this edition compatibility analyzes the Version Description file of any one component software, and according to the current version information of any one component software, the previous release information of this any one component software, the compatibility of the current version information of this any one component software and the previous release information of this any one component software marks, and the old version information of this any one component software, form the edition tree of this any one component software, wherein, v ion can represent by the data structure of following N-ary tree:
It should be noted that, the edition tree of any one component software in the embodiment of the present invention is the initial version that records from Version Description file until the edition tree of all versions of current version.
Exemplary, be illustrated in figure 5 the edition tree of single component software, according to the information in the Version Description file of this single component software, according to N-ary tree structure, from the edition tree that can derive the version information of different branch the initial version V1.0 to current version V1.7 of this single component software, wherein, compatible edition upgrading solid arrow represents, not compatible edition upgrading dotted arrow represents.
The judgment means of S10322, edition compatibility, according to the edition tree between any version of any one component software, judges that whether this any one component software is compatible by the version relied on.
After edition tree between any version that the judgment means of edition compatibility generates any one component software, the judgment means of this edition compatibility by the branched structure of the edition tree between any version of any one component software, can judge that whether this any one component software is compatible by the version relied on.
Concrete, in the edition tree between any version of any one component software, judge any one component software by any two versions of relying on are in compatible branch time, this any one component software is by any two edition compatibilities relied on.
In edition tree between any version of any one component software, judge any one component software by any two versions of relying on are not in compatible branch time, this any one component software is by any two incompatible versions relied on.
Exemplary, suppose that component software system is made up of MASTER, SLAVE and IEC103, and due to as shown in Figure 6, in the version dependence graph of component software version, MASTER by the version information that other assembly relies on is: V1.3, V1.2, and the current version information of MASTER is V1.3; SLAVE by the version information that other assembly relies on is: V1.1, V1.0, and the current version information of SLAVE is V1.2; IEC103 is not relied on by other assembly, and the current version information of IEC103 is V1.1.Therefore, the judgment means of edition compatibility is by judging that the edition compatibility of MASTER, SLAVE and IEC103 judges the compatibling problem of this component software.By the edition tree separately of MASTER, SLAVE and IEC103 in Fig. 6, can learn: MASTER is compatible from the branch of initial version V1.0-V1.1-V1.2-current version V1.3, and SLAVE is compatible from the branch of initial version V1.0-V1.1-current version V1.2, IEC103 is compatible from the branch of initial version V1.0-current version V1.1.Therefore, the judgment means of edition compatibility judges to draw: version information V1.3 and V1.2 that MASTER is relied on by other assembly is compatible; Version information V1.1 and V1.0 that SLAVE is relied on by other assembly is compatible.
Further, as shown in Figure 7, the judgment means of edition compatibility is according to the edition tree between any version of any one component software, and judge that this any one component software is by after the version that relies on whether compatibility, the method also comprises step S104, specific as follows:
Each component software in S104, N number of component software by rely on any two edition compatibilities time, the edition compatibility of the judgment means determination component software system of edition compatibility.
It should be noted that, the judgment means of edition compatibility is judging that any one component software is by after any two edition compatibilities of relying on, if each component software in N number of component software is by any two edition compatibilities relied on, and can develop to the current version of this each component software, then carry out the version merger of each component software, like this, the judgment means of edition compatibility can be judged as that this each component software meets the dependence requirement of other component software, in component software system, the version of this single component software is compatible, then the judgment means of this edition compatibility just can determine that the version of component software system is compatible.
Exemplary, as shown in Figure 6, suppose that the version V1.3 of MASTER is the new version issued, the current version information of MASTER is V1.3, the current version information of SLAVE is V1.2, the current version information of IEC103 is V1.1, and the judgment means due to edition compatibility judges to draw: version information V1.3 and V1.2 that MASTER is relied on by other assembly is compatible; Version information V1.1 and V1.0 that SLAVE is relied on by other assembly is compatible, therefore, the V1.2 version of MASTER can merger be current version information be V1.3, the V1.0 version of SLAVE can merger be current version information be V1.2, therefore, MASTER uses current version information to be V1.3, SLAVE uses current version information to be V1.2, when IEC103 uses current version information for V1.1, the version of this component software system is compatible, and then MASTER is when carrying out the edition upgrading of V1.3, the system of this component software be stable.
The determination methods of a kind of edition compatibility that the embodiment of the present invention provides, the judgment means of edition compatibility obtains the integrated configuration file of component software system, integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, and N number of component software comprises the component software of at least one upgrading; Obtain the Version Description file of N number of component software; According to the Version Description file of component software each in N number of component software, judge that whether any version of each component software is compatible, to determine the stable upgrading carrying out component software system.Adopt above-mentioned technic relization scheme, when judgment means due to edition compatibility has the component software of redaction to upgrade in component software system, first judge that whether any version of each component software in component software system is compatible, and then judge that whether each component software is compatible by the version relied on, thus can determine that whether the version of these software systems when using the component software of upgrading be compatible, therefore, compatibility determination is completed by the judgment means of edition compatibility, component software system can be made when edition compatibility to carry out the edition upgrading of single component software, thus ensure that the stability of component software system upgrade.
Embodiment two
As shown in Figure 8, embodiments of the invention provide a kind of judgment means 1 of edition compatibility, and the judgment means 1 of this edition compatibility can comprise:
Acquiring unit 10, for obtaining the integrated configuration file of component software system, described integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, and described N number of component software comprises the component software of at least one upgrading, wherein, N >=1.
Described acquiring unit 10, also for obtaining the Version Description file of described N number of component software;
Judging unit 11, for the Version Description file according to each component software in described N number of component software of described acquiring unit 10 acquisition, judges that whether any version of described each component software is compatible, determines the stable upgrading carrying out described component software system.
Optionally, as shown in Figure 9, the Version Description file of described each component software that described acquiring unit 10 obtains comprises: the dependence between other N-1 component software in each component software and described N number of component software except self; The judgment means 1 of described edition compatibility, also comprises: determining unit 12.
Described determining unit 12, for the dependence between each component software of obtaining according to described acquiring unit 10 and described other N-1 component software, determines that described each component software is by the version relied on.
Described judging unit 11, whether compatible by the version relied on specifically for judging described each component software that described determining unit 12 is determined.
Optionally, as shown in Figure 10, the Version Description file of any one component software in described N number of component software that described acquiring unit 10 obtains also comprises: the compatibility of the current version information of any one component software described, the previous release information of any one component software described, the current version information of any one component software described and the previous release information of any one component software described marks, and the old version information of any one component software described; The judgment means 1 of described edition compatibility also comprises: generation unit 13.
Generation unit 13, compatibility for the previous release information of the current version information of any one component software described in obtaining according to described acquiring unit 10, the previous release information of any one component software described, the current version information of any one component software described and any one component software described marks, and the old version information of any one component software described, the edition tree between any version of any one component software described in generating.
Described judging unit 11, also specifically for any one component software described in generating according to described generation unit 13 any version between edition tree, judge that whether any one component software described that described determining unit 12 is determined compatible by the version relied on.
Optionally, judging unit 11, also specifically in the edition tree between any version of any one component software described in described generation unit 13 generation, any one component software described by any two versions of relying on are in compatible branch time, any one component software described is by any two edition compatibilities relied on.
Optionally, described determining unit 12, also judge that any one component software described is by after any two edition compatibilities of relying on for described judging unit 11, described judging unit 11 judge described each component software in described N number of component software by rely on any two edition compatibilities time, determine the edition compatibility of described component software system.
The judgment means of a kind of edition compatibility that the embodiment of the present invention provides, the judgment means of this edition compatibility obtains the integrated configuration file of component software system, integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, N number of component software comprises the component software of at least one upgrading; Obtain the Version Description file of N number of component software; According to the Version Description file of component software each in N number of component software, judge that whether any version of each component software is compatible, to determine the stable upgrading carrying out component software system.Adopt above-mentioned technic relization scheme, when judgment means due to edition compatibility has the component software of redaction to upgrade in component software system, first judge that whether any version of each component software in component software system is compatible, and then judge that whether each component software is compatible by the version relied on, thus can determine that whether the version of these software systems when using the component software of upgrading be compatible, therefore, by the compatibility determination that the judgment means of edition compatibility completes, component software system can be made when edition compatibility to carry out the edition upgrading of single component software, thus ensure that the stability of component software system upgrade.
Embodiment three
As shown in figure 11, embodiments of the invention provide a kind of computing machine, and this computing machine can comprise:
Processor 14 and storer 15, wherein, storer 15 is connected with processor 14, and such as, storer 15 can be connected by bus with processor 14.
Storer 15 is for storing the executable program code of computing machine, this program code comprises computer-managed instruction, storer 15 may comprise high-speed RAM storer, also nonvolatile memory (non-volatile memory) may also be comprised, such as, at least one magnetic disk memory.
Processor 14 can be central processing unit, or specific integrated circuit, or is configured to implement one or more integrated circuit of the present invention.
Concrete, described processor 14, can be used for the integrated configuration file obtaining component software system, described integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, described N number of component software comprises the component software of at least one upgrading, wherein, N >=1; And obtain the Version Description file of described N number of component software; And according to the Version Description file of each component software in described N number of component software, judge that whether any version of described each component software compatible, determine the stable upgrading carrying out described component software system; Described storer 15, can be used for the integrated configuration file and the software code thereof that store described N number of component software that described processor 14 obtains, and the Version Description file of described N number of component software and software code thereof, and store the software program that the described computing machine of control completes said process, thus make described processor 14 by performing above-mentioned software program and calling above-mentioned software code, complete said process.
Optionally, the Version Description file of described each component software that described processor 14 obtains comprises: go out the dependence between other N-1 component software beyond self in each component software and described N number of component software.
Described processor 14, also for according to the dependence between each component software and described other N-1 component software, determines that described each component software is by the version relied on.
Described processor 14, specifically for judging that whether described each component software is compatible by the version relied on.
Optionally, the Version Description file of any one component software in described N number of component software that described processor 14 obtains also comprises: the compatibility of the current version information of any one component software described, the previous release information of any one component software described, the current version information of any one component software described and the previous release information of any one component software described marks, and the old version information of any one component software described.
Processor 14, compatibility also specifically for the previous release information of the previous release information of the current version information according to any one component software described, any one component software described, the current version information of any one component software described and any one component software described marks, and the old version information of any one component software described, the edition tree between any version of any one component software described in generating.
Described processor 14, also specifically for any one component software described in basis any version between edition tree, judge that whether any one component software described compatible by the version relied on.
Optionally, processor 14, also specifically in the edition tree between any version of any one component software described, any one component software described by any two versions of relying on are in compatible branch time, any one component software described is by any two edition compatibilities relied on.
Optionally, described processor 14, also for any one component software described by after any two edition compatibilities of relying on, the described each component software in described N number of component software by rely on any two edition compatibilities time, determine the edition compatibility of described component software system.
A kind of computing machine that the embodiment of the present invention provides, this computing machine obtains the integrated configuration file of component software system, integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, and N number of component software comprises the component software of at least one upgrading; Obtain the Version Description file of N number of component software; According to the Version Description file of component software each in N number of component software, judge that whether any version of each component software is compatible, to determine the stable upgrading carrying out component software system.Adopt above-mentioned technic relization scheme, due to computing machine in component software system, have the component software of redaction to upgrade time, first judge that whether any version of each component software in component software system is compatible, and then judge that whether each component software is compatible by the version relied on, thus can determine that whether the version of these software systems when using the component software of upgrading be compatible, therefore, compatibility determination is completed by computing machine, component software system can be made when edition compatibility to carry out the edition upgrading of single component software, thus ensure that the stability of component software system upgrade.
Those skilled in the art should understand, embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt the form of hardware embodiment, software implementation or the embodiment in conjunction with software and hardware aspect.And the present invention can adopt in one or more form wherein including the upper computer program implemented of computer-usable storage medium (including but not limited to magnetic disk memory and optical memory etc.) of computer usable program code.
The present invention describes with reference to according to the process flow diagram of the method for the embodiment of the present invention, equipment (system) and computer program and/or block scheme.Should understand can by the combination of the flow process in each flow process in computer program instructions realization flow figure and/or block scheme and/or square frame and process flow diagram and/or block scheme and/or square frame.These computer program instructions can being provided to the processor of multi-purpose computer, special purpose computer, Embedded Processor or other programmable data processing device to produce a machine, making the instruction performed by the processor of computing machine or other programmable data processing device produce device for realizing the function of specifying in process flow diagram flow process or multiple flow process and/or block scheme square frame or multiple square frame.
These computer program instructions also can be stored in can in the computer-readable memory that works in a specific way of vectoring computer or other programmable data processing device, the instruction making to be stored in this computer-readable memory produces the manufacture comprising command device, and this command device realizes the function of specifying in process flow diagram flow process or multiple flow process and/or block scheme square frame or multiple square frame.
These computer program instructions also can be loaded in computing machine or other programmable data processing device, make on computing machine or other programmable devices, to perform sequence of operations step to produce computer implemented process, thus the instruction performed on computing machine or other programmable devices is provided for the step realizing the function of specifying in process flow diagram flow process or multiple flow process and/or block scheme square frame or multiple square frame.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.
Claims (10)
1. a determination methods for edition compatibility, is characterized in that, described method comprises:
Obtain the integrated configuration file of component software system, described integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, and described N number of component software comprises the component software of at least one upgrading, wherein, and N >=1;
Obtain the Version Description file of described N number of component software;
According to the Version Description file of each component software in described N number of component software, judge that whether any version of described each component software is compatible, determine the stable upgrading carrying out described component software system.
2. the determination methods of edition compatibility according to claim 1, it is characterized in that, the Version Description file of described each component software comprises: the dependence between other N-1 component software in each component software and described N number of component software except self;
Accordingly, the described Version Description file according to each component software in described N number of component software, judges that whether any version of described each component software is compatible, comprising:
According to the dependence between each component software and described other N-1 component software, determine that described each component software is by the version relied on;
Judge that whether described each component software is compatible by the version relied on.
3. the determination methods of edition compatibility according to claim 2, it is characterized in that, the Version Description file of any one component software in described N number of component software also comprises: the compatibility of the current version information of any one component software described, the previous release information of any one component software described, the current version information of any one component software described and the previous release information of any one component software described marks, and the old version information of any one component software described;
Accordingly, judge that any one component software described is by the whether compatible method of the version that relies on, comprising:
Compatibility according to the previous release information of the previous release information of the current version information of any one component software described, any one component software described, the current version information of any one component software described and any one component software described marks, and the old version information of any one component software described, the edition tree between any version of any one component software described in generating;
According to the edition tree between any version of any one component software described, judge that whether any one component software described is compatible by the version relied on.
4. the determination methods of edition compatibility according to claim 3, is characterized in that, the edition tree between any version of any one component software described in described basis, judges that whether any one component software described is compatible by the version relied on, comprising:
In edition tree between any version of any one component software described, judge any one component software described by any two versions of relying on are in compatible branch time, any one component software described is by any two edition compatibilities relied on.
5. the determination methods of edition compatibility according to claim 4, is characterized in that, any one component software described is by after any two edition compatibilities of relying on, and described method also comprises:
Described each component software in described N number of component software by rely on any two edition compatibilities time, determine the edition compatibility of described component software system.
6. a judgment means for edition compatibility, is characterized in that, described device comprises:
Acquiring unit, for obtaining the integrated configuration file of component software system, described integrated configuration file comprises the configuration information of N number of component software when described component software system is upgraded, and described N number of component software comprises the component software of at least one upgrading, wherein, N >=1;
Described acquiring unit, also for obtaining the Version Description file of described N number of component software;
Judging unit, for the Version Description file of each component software in described N number of component software of obtaining according to described acquiring unit, judges that whether any version of described each component software is compatible, determines the stable upgrading carrying out described component software system.
7. the judgment means of edition compatibility according to claim 6, it is characterized in that, the Version Description file of described each component software that described acquiring unit obtains comprises: the dependence between other N-1 component software in each component software and described N number of component software except self; The judgment means of described edition compatibility, also comprises: determining unit;
Described determining unit, for the dependence between each component software of obtaining according to described acquiring unit and described other N-1 component software, determines that described each component software is by the version relied on;
Described judging unit, whether compatible by the version relied on specifically for judging described each component software that described determining unit is determined.
8. the judgment means of edition compatibility according to claim 7, it is characterized in that, the Version Description file of any one component software in described N number of component software that described acquiring unit obtains also comprises: the compatibility of the current version information of any one component software described, the previous release information of any one component software described, the current version information of any one component software described and the previous release information of any one component software described marks, and the old version information of any one component software described; The judgment means of described edition compatibility also comprises: generation unit;
Generation unit, compatibility for the previous release information of the current version information of any one component software described in obtaining according to described acquiring unit, the previous release information of any one component software described, the current version information of any one component software described and any one component software described marks, and the old version information of any one component software described, the edition tree between any version of any one component software described in generating;
Described judging unit, also specifically for any one component software described in generating according to described generation unit any version between edition tree, judge that whether any one component software described that described determining unit is determined compatible by the version relied on.
9. the judgment means of edition compatibility according to claim 8, is characterized in that,
Judging unit, also specifically for any one component software described in generating at described generation unit any version between edition tree in, any one component software described by any two versions of relying on are in compatible branch time, any one component software described is by any two edition compatibilities relied on.
10. the judgment means of edition compatibility according to claim 9, is characterized in that,
Described determining unit, also judge that any one component software described is by after any two edition compatibilities of relying on for described judging unit, described judging unit judge described each component software in described N number of component software by rely on any two edition compatibilities time, determine the edition compatibility of described component software system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510283911.4A CN104881311B (en) | 2015-05-28 | 2015-05-28 | The judgment method and device of a kind of edition compatibility |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510283911.4A CN104881311B (en) | 2015-05-28 | 2015-05-28 | The judgment method and device of a kind of edition compatibility |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104881311A true CN104881311A (en) | 2015-09-02 |
| CN104881311B CN104881311B (en) | 2018-06-08 |
Family
ID=53948817
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510283911.4A Expired - Fee Related CN104881311B (en) | 2015-05-28 | 2015-05-28 | The judgment method and device of a kind of edition compatibility |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104881311B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293763A (en) * | 2016-08-19 | 2017-01-04 | 广州唯品会信息科技有限公司 | The management method of application component version and device |
| CN106325921A (en) * | 2016-08-16 | 2017-01-11 | 北京奇虎科技有限公司 | Method and device for releasing associated plugins |
| CN107656749A (en) * | 2017-09-26 | 2018-02-02 | 国网江苏省电力公司 | A kind of device version management-control method and device |
| CN108170465A (en) * | 2018-01-04 | 2018-06-15 | 武汉斗鱼网络科技有限公司 | A kind of version information management method, electronic equipment and readable storage medium storing program for executing |
| WO2019061067A1 (en) * | 2017-09-27 | 2019-04-04 | Intel Corporation | Firmware component with self-descriptive dependency information |
| CN112947956A (en) * | 2020-08-31 | 2021-06-11 | 深圳市明源云科技有限公司 | Application software upgrading method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030145315A1 (en) * | 2002-01-23 | 2003-07-31 | Tuomo Aro | Exchange of data between components of distributed software having different versions of software |
| US20070006222A1 (en) * | 2005-06-21 | 2007-01-04 | Henning Maier | Software installation method and computer system |
| CN1908901A (en) * | 2005-04-29 | 2007-02-07 | 阿尔卡特公司 | Electronic device configuration management systems and methods |
| CN1936844A (en) * | 2005-09-23 | 2007-03-28 | 三星电子株式会社 | Method and system for updating software |
| CN102708044A (en) * | 2011-03-23 | 2012-10-03 | 沃尔沃汽车公司 | Complete and compatible function |
-
2015
- 2015-05-28 CN CN201510283911.4A patent/CN104881311B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030145315A1 (en) * | 2002-01-23 | 2003-07-31 | Tuomo Aro | Exchange of data between components of distributed software having different versions of software |
| CN1908901A (en) * | 2005-04-29 | 2007-02-07 | 阿尔卡特公司 | Electronic device configuration management systems and methods |
| US20070006222A1 (en) * | 2005-06-21 | 2007-01-04 | Henning Maier | Software installation method and computer system |
| CN1936844A (en) * | 2005-09-23 | 2007-03-28 | 三星电子株式会社 | Method and system for updating software |
| CN102708044A (en) * | 2011-03-23 | 2012-10-03 | 沃尔沃汽车公司 | Complete and compatible function |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106325921A (en) * | 2016-08-16 | 2017-01-11 | 北京奇虎科技有限公司 | Method and device for releasing associated plugins |
| CN106293763A (en) * | 2016-08-19 | 2017-01-04 | 广州唯品会信息科技有限公司 | The management method of application component version and device |
| CN106293763B (en) * | 2016-08-19 | 2019-10-22 | 广州品唯软件有限公司 | The management method and device of application component version |
| CN107656749A (en) * | 2017-09-26 | 2018-02-02 | 国网江苏省电力公司 | A kind of device version management-control method and device |
| WO2019061067A1 (en) * | 2017-09-27 | 2019-04-04 | Intel Corporation | Firmware component with self-descriptive dependency information |
| US11249748B2 (en) | 2017-09-27 | 2022-02-15 | Intel Corporation | Firmware component with self-descriptive dependency information |
| US11875147B2 (en) | 2017-09-27 | 2024-01-16 | Intel Corporation | Firmware component with self-descriptive dependency information |
| CN108170465A (en) * | 2018-01-04 | 2018-06-15 | 武汉斗鱼网络科技有限公司 | A kind of version information management method, electronic equipment and readable storage medium storing program for executing |
| CN112947956A (en) * | 2020-08-31 | 2021-06-11 | 深圳市明源云科技有限公司 | Application software upgrading method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104881311B (en) | 2018-06-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11256523B2 (en) | Modular co-versioning in a dynamically linked runtime environment | |
| CN104881311A (en) | Method and apparatus for judging version compatibility | |
| CN104793946B (en) | Dispositions method and system are applied based on cloud computing platform | |
| CN107615239B (en) | Infrastructure for hosting and publishing software packages | |
| CN107733985B (en) | Method and device for deploying functional components of cloud computing system | |
| CN102508669A (en) | Automatic program code generating method | |
| CN109324799A (en) | A kind of code compiling method, computer installation and computer readable storage medium | |
| CN104866298A (en) | Flow chart based process business implementing method and device | |
| CN111857801B (en) | Construction method of mobile application | |
| CN103645900A (en) | Method and device for releasing software | |
| CN105446712A (en) | Defect mending method and device for application program | |
| CN109614325B (en) | Method and device for determining control attribute, electronic equipment and storage medium | |
| US20110321030A1 (en) | Method and apparatus for updating a software image | |
| CN108694049B (en) | Method and equipment for updating software | |
| CN105678118B (en) | A kind of software version generation method and device containing digital certificate | |
| CN104598382A (en) | Test control method and device | |
| CN111858359B (en) | Method and device for acquiring engineering code position of executable file | |
| CN110968339B (en) | Method and device for front-end building tool and electronic equipment | |
| CN109144524B (en) | Version release method of subject game on education platform and electronic equipment | |
| CN111176912A (en) | Relay protection device hardware configuration information management system and method | |
| CN106547548B (en) | Software version compiling method and device | |
| CN113741931B (en) | Software upgrading method and device, electronic equipment and readable storage medium | |
| CN105867894A (en) | Automatic creating method and system of development environment | |
| CN112307589B (en) | Unit working condition creation method and device, electronic equipment and storage medium | |
| CN107291439A (en) | A kind of target delta data construction method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20180608 |