CN115981689A - Method for realizing arranging and upgrading based on component version number field analysis strategy - Google Patents
Method for realizing arranging and upgrading based on component version number field analysis strategy Download PDFInfo
- Publication number
- CN115981689A CN115981689A CN202211675061.9A CN202211675061A CN115981689A CN 115981689 A CN115981689 A CN 115981689A CN 202211675061 A CN202211675061 A CN 202211675061A CN 115981689 A CN115981689 A CN 115981689A
- Authority
- CN
- China
- Prior art keywords
- version number
- upgraded
- version
- upgrade
- software product
- 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.)
- Pending
Links
Images
Abstract
The invention provides a method for realizing arranging and upgrading based on a component version number field analysis strategy. The method comprises the following steps: the method comprises the steps of predefining version information of a software product to be upgraded, and then generating a component version number of the software product in advance according to the version information of the software product to be upgraded; loading version information of the upgrade package group; analyzing the component version number of the software product to be upgraded to obtain version information of the software product, comparing the version information of the upgrade package group with the version information of the software product to be upgraded, judging whether the currently loaded upgrade package group can be used for upgrading the software product to be upgraded according to a comparison result, and if so, arranging and upgrading according to a set rule, wherein the method specifically comprises the following steps: traversing all the upgrade packages in the upgrade package group, sequencing all the upgrade packages, traversing the upgrade packages which are sequenced from small to large, and upgrading from the first upgrade package which is found to be smaller than the software version of the software product to be upgraded.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method for realizing arrangement and upgrading based on a component version number field analysis strategy.
Background
At present, large software aims at private network users, and cannot be updated in real time due to high customization degree. When upgrading is required, usually, an operator needs to be sent out independently, a plurality of specified upgrading packages are searched from the software library, and the upgrading sequence is organized according to the version number and is operated manually.
Since the upgrade operation actions need to be executed one by one, the next one is executed after each upgrade package is executed, which consumes labor and introduces a risk of problems.
Disclosure of Invention
The invention provides a method for realizing arranging and upgrading based on a component version number field analysis strategy, aiming at the problem that manual operation is needed to upgrade user software in the existing private network environment.
The invention provides a method for realizing arranging and upgrading based on a component version number field analysis strategy, which comprises the following steps:
predefining version information of a software product to be upgraded, and then generating a component version number of the software product in advance according to the version information; the version information of the software product to be upgraded comprises a product name, a main version number, a customized number and a customized version number;
loading version information of the upgrade package group; the upgrade package group is a large software package used for indicating the initial upgrade package, the upgrade package sequence and the upgrade ending version of the software product to be upgraded, and the version information of the upgrade package group comprises a product name, the lowest main version number allowed to be upgraded, the highest main version number in the package group, a customized number, the lowest customized version number allowed to be upgraded and the highest customized version number in the package group;
analyzing the component version number of the software product to be upgraded to obtain version information of the software product, comparing the version information of the upgrade package group with the version information of the software product to be upgraded, judging whether the currently loaded upgrade package group can be used for upgrading the software product to be upgraded according to a comparison result, and if so, arranging and upgrading according to a set rule, wherein the method specifically comprises the following steps: traversing all the upgrade packages in the upgrade package group, sequencing all the upgrade packages, traversing the upgrade packages which are sequenced from small to large, and upgrading from the first upgrade package which is found to be smaller than the software version of the software product to be upgraded; the sorting mode specifically comprises the following steps: the method comprises the steps of firstly arranging the major version numbers in a sequence from low to high, if the major version numbers are consistent, arranging the non-baseline versions in the customized numbers in a sequence behind the baseline version, and if the customized numbers or the baseline numbers are consistent, arranging the customized version numbers in a sequence from low to high.
Further, judging whether the currently loaded upgrade package group can be used for upgrading the software product to be upgraded according to the comparison result, specifically comprising:
step A1: if the product names of the upgrade package group and the software product to be upgraded are not consistent, upgrading cannot be performed; otherwise, continuing the subsequent comparison;
step A2: if the major version number of the software product to be upgraded is smaller than the lowest major version number allowed to be upgraded, or the major version number of the software product to be upgraded is larger than the highest major version number in the package group, the software product to be upgraded cannot be upgraded; otherwise, continuing the subsequent comparison;
step A3: if the upgrade package group is not consistent with the customized serial numbers of the upgrade software products, the upgrade cannot be performed; otherwise, continuing the subsequent comparison;
step A4: if the customized version number of the software product to be upgraded is smaller than the lowest customized version number allowed to be upgraded, or the customized version number of the software product to be upgraded is larger than the highest customized version number in the package group, the software product to be upgraded cannot be upgraded; otherwise, the upgrade can be performed.
Further, in the step A3, if the customized numbers of the upgrade package group and the upgrade software product are consistent and are both baseline versions, the upgrade can be performed without continuing the subsequent comparison; if the upgrade package group and the upgrade software product's custom number are consistent but not the baseline version, then the subsequent comparisons continue.
Further, the pre-generating of the component version number according to the version information specifically includes: and arranging according to the sequence of the major version number, the customized serial number and the customized version number, and separating every two by adopting the characteristic symbols to finally form the corresponding component version number.
Further, the major version number is composed of a major version number, a middle version number and a minor version number; the large version number is used for indicating the incompatible updating times or the software reinstallation times; the middle version number is used for indicating the times of product component replacement, function addition and function change; the small version number is used for indicating the times of other smaller change cases except the cases indicated by the large version number and the medium version number.
Further, for the customized numbers, a helper character approach is employed to distinguish between the baseline version and the customized version.
The invention has the beneficial effects that:
1. by designing the version numbers of the components for the software products, the upgrading packages can be skillfully arranged in a good sequence at one time, so that the upgrading program can automatically arrange the upgrading starting position and the upgrading sequence according to all packages in the upgrading package group and the version numbers before self upgrading, and the software upgrading efficiency is improved;
2. compared with the method of manually organizing the upgrade package sequence, selecting and then manually operating, the method has the advantages that labor cost can be saved, time for waiting for program operation delay of personnel is shortened, and the risk of maintenance accidents caused by human errors is reduced.
Drawings
Fig. 1 is a schematic flowchart of a method for implementing an orchestration and upgrade based on a component version number field parsing policy according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
Before the technical scheme of the invention is introduced, related concepts are briefly explained.
Upgrading the package: a software package that completes the upgrade task for a single version;
upgrading the package group: the software upgrading system comprises a large software package which internally contains a plurality of upgrading packages and has the function of autonomously judging from which upgrading package the target software is supposed to start, according to which sequence and upgrading to which version is finished.
The product name is as follows: the product numbers identified in the upgrade package and the installed software version information are used to distinguish between different software products.
Baseline version: software release a versioned version of the software for all general cases.
Non-baseline version: in the delivery process of the software to a client, the product is customized and developed according to the customization requirements of the client, and the release version of the product is developed and customized based on a certain baseline version.
Customizing a number: a field used to identify whether the software package is a baseline version of an upgrade package or a custom version of an upgrade package.
Major version number: the baseline version number is referred to as the major version number.
Customizing the version number: in the non-baseline version, the version number of the software version is customized and released on the basis of a certain main version number.
The lowest major version number allowed to be upgraded in the packet group: and judging whether the software to be upgraded meets the main version number required by the lowest version of the upgrade, wherein the main version number is generally the previous version of the minimum main version number in the upgrade package in the package group.
The highest major version number allowed to be upgraded in the packet group: and judging whether the software to be upgraded meets the main version number required by the highest version of the upgrade, wherein the main version number is generally the second largest main version number in the upgrade package in the package group.
The lowest custom version number allowed to be upgraded within a package group: and judging whether the software to be upgraded meets the customized version number required by the lowest version of the upgrade, wherein the customized version number is generally the previous version of the minimum customized version number in the upgrade package in the package group.
The highest custom version number allowed to be upgraded within the package group: and judging whether the software to be upgraded meets the customized version number required by the highest version upgrade, wherein the customized version number is generally the second largest customized version number in the upgrade package in the package group.
Example 1
As shown in fig. 1, an embodiment of the present invention provides a method for implementing an orchestration and upgrade based on a component version number field resolution policy, including the following steps:
s101: predefining version information of a software product to be upgraded, and then generating a component version number of the software product in advance according to the version information; the version information of the software product to be upgraded comprises a product name, a main version number, a customized serial number and a customized version number;
specifically, as an implementable embodiment, the pre-generating the component version number according to the version information includes: and arranging according to the sequence of the product name, the main version number, the customized serial number and the customized version number, and separating every two by adopting the characteristic symbols to finally form the corresponding component version number.
In the main version number, in order to distinguish the magnitude of the degree of change of the software product itself, the software product is designed to be composed of three sub-version numbers, namely: a large version number, a medium version number and a small version number; the large version number is used for indicating incompatible updating times or software reinstallation times; the medium version number is used for indicating the times of product component replacement, function addition and function change; the small version number is used for indicating the times of other smaller change cases except the case indicated by the large version number and the medium version number.
Furthermore, the baseline version and the customized version are distinguished by using a helper character (for example, 0basic mentioned below) for the customized numbers, which is advantageous in that the upgrade package is convenient to sort.
S102: loading version information of the upgrade package group; the upgrade package group is a large software package used for indicating the initial upgrade package, the upgrade package sequence and the upgrade ending version of the software product to be upgraded, and the version information of the upgrade package group comprises a product name, the lowest main version number allowed to be upgraded, the highest main version number in the package group, a customized number, the lowest customized version number allowed to be upgraded and the highest customized version number in the package group;
specifically, the upgrade package group is decompressed and the version information file of the upgrade package group is fetched, and the following information is parsed according to the file: product name (used to determine whether a product broad class is eligible for upgrade), custom number (used to determine whether a product standard branch or a custom branch), product version number (consisting of "major version number" + "custom branch version number").
S103: analyzing the component version number of the software product to be upgraded to obtain version information of the software product, comparing the version information of the upgrade package group with the version information of the software product to be upgraded, judging whether the currently loaded upgrade package group can be used for upgrading the software product to be upgraded according to a comparison result, and if so, arranging and upgrading according to a set rule, wherein the method specifically comprises the following steps of: traversing all the upgrade packages in the upgrade package group, sequencing all the upgrade packages, traversing the upgrade packages which are sequenced from small to large, and upgrading from the first upgrade package which is found to be smaller than the software version of the software product to be upgraded; the sorting mode specifically comprises the following steps: the method comprises the steps of firstly arranging the major version numbers in a sequence from low to high, if the major version numbers are consistent, arranging the non-baseline versions in a sequence behind the baseline version, and if the customized numbers or the baseline numbers are consistent, arranging the customized version numbers in a sequence from low to high.
The method for realizing the arrangement and the upgrade based on the analysis strategy of the version number field of the component can automatically identify the minimum position of the upgrade package which is allowed to be upgraded and upgrade the version package from the proper version to the latest version. In addition, by using the auxiliary character mode, the field specification design that the baseline version is ordered in preference to the customized version is realized.
Example 2
On the basis of the above embodiment, it is assumed that the format of the version number of the upgrade package is: "vx.y.z-xxxxxx-vy.z", where "-" represents a feature separating the version information of adjacent fields.
Y.z "is a major version number (used to determine which major version the software product is), V" indicates the beginning of the major version number, X "indicates a major version number (the version number is typically changed only when the software product is subjected to an upgrade operation for incompatible updates or programs that require reinstallation of the software), Y" indicates a medium version number (the version number is typically changed when there is a component replacement, or a new function is added or changed), and Z "indicates a small version number (the version number is typically changed when there is a change in a function that is not a major version, or a patch upgrade that does not involve a change in the core components of the software product).
"xxxxxx" represents a custom number, which in this embodiment is composed of a minimum of 3 and a maximum of 6 letters; it should be noted that, in the case of the baseline version, the position adopts a special number (e.g., "0 basic") to distinguish the baseline version from the customized version.
"vy.z" denotes a custom version number (which will generally be followed by a custom number only if the custom number is not the special number mentioned above); where "Y" indicates the presence in the custom branch (the version number will typically only be changed if a functional join or iterative update unique to the custom branch occurs). The "X" representation appears in the custom branch (the version number is typically changed only if a change of a non-primary module unique to the custom branch occurs).
Based on the above format of the component version number, in the embodiment of the present invention, analyzing the component version number of the software product to be upgraded to obtain the version information specifically includes: intercepting the first field according to a characteristic symbol (such as "-" mentioned above) to obtain a main version number; intercepting a second field to obtain a customized number; intercepting a third field to obtain a customized version number; next, comparing the version information of the upgrade package group with the version information of the software product to be upgraded, and then judging whether the currently loaded upgrade package group can be used for upgrading the software product to be upgraded according to the comparison result, which specifically comprises:
step A1: if the product names of the upgrade package group and the software product to be upgraded are not consistent, upgrading cannot be performed; otherwise, continuing the subsequent comparison;
step A2: if the major version number of the software product to be upgraded is smaller than the lowest major version number allowed to be upgraded, or the major version number of the software product to be upgraded is larger than the highest major version number in the package group, the software product to be upgraded cannot be upgraded; otherwise, continuing the subsequent comparison;
specifically, if the major version number of the software product to be upgraded is smaller than the lowest major version number allowed to be upgraded, it indicates that the software product to be upgraded still needs to upgrade other product packages to a certain version state before the upgrade package group can be used, and at this time, the software product cannot be upgraded. If the major version number of the software product to be upgraded is larger than the highest major version number in the package group, the software product version to be upgraded does not need to be upgraded by using the upgrade package group, and the upgrade exits.
Step A3: if the upgrade package group is not consistent with the customized serial numbers of the upgrade software products, the upgrade cannot be performed; otherwise, continuing the subsequent comparison;
specifically, if the upgrade package group and the upgrade software product have the same customized serial numbers and are baseline versions, the upgrade can be performed without continuing the subsequent comparison; if the upgrade package group and the customized serial numbers of the upgraded software product are identical but not baseline versions, the subsequent comparison continues.
Step A4: if the customized version number of the software product to be upgraded is smaller than the lowest customized version number allowed to be upgraded, or the customized version number of the software product to be upgraded is larger than the highest customized version number in the package group, the software product to be upgraded cannot be upgraded; otherwise, the upgrade can be performed.
Specifically, according to the comparison process described above, there are two cases where the upgrade can be performed using the upgrade package group: the first case is: when the product names of the upgrading package group and the software product to be upgraded are consistent, the main version number of the software product to be upgraded is not less than the lowest main version number allowed to be upgraded and not more than the highest main version number in the package group, the customized numbers of the upgrading package group and the upgrading software product are consistent and are both baseline versions, and the upgrading can be carried out by using the upgrading package group; the second case is: when the product names of the upgrade package group and the software product to be upgraded are consistent, the major version number of the software product to be upgraded is not less than the lowest major version number allowed to be upgraded and not more than the highest major version number in the package group, the customized numbers of the upgrade package group and the upgrade software product are consistent but not baseline versions, and the customized version number of the software product to be upgraded is not less than the lowest customized version number allowed to be upgraded and not more than the highest customized version number in the package group, the upgrade package group can be used for upgrading.
On the basis of the above content, the arrangement and upgrade are performed according to the set rule, which specifically includes: traversing all the upgrade packages in the upgrade package group, sequencing all the upgrade packages, traversing the upgrade packages which are sequenced from small to large, and upgrading from the first upgrade package which is found to be smaller than the software version of the software product to be upgraded; the sorting mode specifically comprises the following steps: the method comprises the steps of firstly arranging the major version numbers in a sequence from low to high, if the major version numbers are consistent, arranging the non-baseline versions in a sequence behind the baseline version, and if the customized numbers or the baseline numbers are consistent, arranging the customized version numbers in a sequence from low to high.
Specifically, when the upgrade is arranged, all the upgrade packages in the upgrade package group are traversed, the names are recorded in the variable-length array, sequencing is started in sequence, and the basic principle of comparing character strings by using a computer is used for reference, wherein the specific comparison and sequencing process is as follows: the character string comparison is ordered according to the ASCII code sequence from left to right; comparing the ASCII code values of the characters at the first position of the two character strings, and if the ASCII code values are the same, comparing the next position; if a certain bit of one string appears for the first time and is larger than the ASCII code value of the same position of the other string, the comparison is quitted and the previous string is judged to be larger than the latter string; if a certain position of a certain character string has characters (strictly speaking, the position is a non-empty character \ 0) and the position of another character string is already finished, quitting comparison and judging that the former character string is larger than the latter character string; if the two are finished at the same time, the characters of each digit from front to back are the same, and the character strings of the two are judged to be the same;
the program does not perform interception and storage operations of any string, and only needs to sort the upgrade packages in the package group according to names.
Since the naming format of the upgrade package is "product name _ major version number-custom version (possibly empty string) _ upgrade package date". Tar.gz "which is specifically arranged, it can be understood that the product names of all upgrade packages in the upgrade package group must be the same, the major version number is first, which guarantees major version number priority weight, and the custom number is a lower case letter string of a specific format, and the first bit of the baseline version is" 0", so that all baseline versions ASCII values must be smaller than other custom versions, which are arranged at the top. The customized version number must be greater than the empty string if there are non-empty characters. Thus, the following effects can be achieved: and sorting the mainline versions from low to high, wherein the mainline versions are the same, the baseline version is preferred, the customized versions are arranged later, the customized numbers are the same, the customized versions are sorted from low to high, after the sequence is arranged, the current product version starts to traverse, and the version which is the first version smaller than the sequence of the upgrade package is found and starts to be upgraded backwards.
According to the method provided by the embodiment of the invention, after the implementer takes the upgrade package group, the implementer only needs to put the upgrade package group into a background environment and execute the upgrade command, and the platform can be automatically arranged and select a proper starting version until the latest version which can be supported is upgraded.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, and not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (6)
1. The method for realizing arranging and upgrading based on the field analysis strategy of the component version number is characterized by comprising the following steps:
the method comprises the steps of predefining version information of a software product to be upgraded, and then generating a component version number of the software product in advance according to the version information of the software product to be upgraded; the version information of the software product to be upgraded comprises a product name, a main version number, a customized serial number and a customized version number;
loading version information of the upgrade package group; the upgrade package group is a large software package used for indicating the initial upgrade package, the upgrade package sequence and the upgrade ending version of the software product to be upgraded, and the version information of the upgrade package group comprises a product name, the lowest main version number allowed to be upgraded, the highest main version number in the package group, a customized number, the lowest customized version number allowed to be upgraded and the highest customized version number in the package group;
analyzing the component version number of the software product to be upgraded to obtain version information of the software product, comparing the version information of the upgrade package group with the version information of the software product to be upgraded, judging whether the currently loaded upgrade package group can be used for upgrading the software product to be upgraded according to a comparison result, and if so, arranging and upgrading according to a set rule, wherein the method specifically comprises the following steps: traversing all the upgrade packages in the upgrade package group, sequencing all the upgrade packages, traversing the upgrade packages which are sequenced from small to large, and upgrading from the first upgrade package which is found to be smaller than the software version of the software product to be upgraded; the sorting mode specifically comprises the following steps: the method comprises the steps of firstly arranging the major version numbers in a sequence from low to high, if the major version numbers are consistent, arranging the non-baseline versions in the customized numbers in a sequence behind the baseline version, and if the customized numbers or the baseline numbers are consistent, arranging the customized version numbers in a sequence from low to high.
2. The method for realizing arranging and upgrading based on the component version number field parsing strategy according to claim 1, wherein judging whether the software product to be upgraded can be upgraded by using the currently loaded upgrade package group according to the comparison result specifically comprises:
step A1: if the product names of the upgrade package group and the software product to be upgraded are not consistent, upgrading cannot be performed; otherwise, continuing the subsequent comparison;
step A2: if the major version number of the software product to be upgraded is smaller than the lowest major version number allowed to be upgraded, or the major version number of the software product to be upgraded is larger than the highest major version number in the package group, the software product to be upgraded cannot be upgraded; otherwise, continuing the subsequent comparison;
step A3: if the upgrade package group is not consistent with the customized serial numbers of the upgrade software products, the upgrade cannot be performed; otherwise, continuing the subsequent comparison;
step A4: if the customized version number of the software product to be upgraded is smaller than the lowest customized version number allowed to be upgraded, or the customized version number of the software product to be upgraded is larger than the highest customized version number in the package group, the software product to be upgraded cannot be upgraded; otherwise, the upgrade can be performed.
3. The method for realizing arranging and upgrading based on the component version number field resolution strategy according to claim 2, wherein in the step A3, if the customized numbers of the upgrade package group and the upgrade software product are consistent and are both baseline versions, the upgrade can be performed without continuing the subsequent comparison; if the upgrade package group and the upgrade software product's custom number are consistent but not the baseline version, then the subsequent comparisons continue.
4. The method for realizing arranging and upgrading based on the field parsing strategy of the component version number according to claim 1, wherein the component version number is generated in advance according to version information thereof, and specifically comprises: and arranging according to the sequence of the major version number, the customized serial number and the customized version number, and separating every two by adopting the characteristic symbols to finally form the corresponding component version number.
5. The method for realizing the arrangement and the upgrade based on the component version number field resolution strategy according to claim 1, wherein the major version number is composed of a major version number, a middle version number and a minor version number; the large version number is used for indicating incompatible updating times or software reinstallation times; the middle version number is used for indicating the times of product component replacement, function addition and function change; the small version number is used for indicating the times of other smaller change cases except the case indicated by the large version number and the medium version number.
6. The method for implementing orchestration and upgrade based on component version number field resolution policies according to claim 1, wherein for custom numbers, an auxiliary character approach is used to distinguish between baseline and custom versions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211675061.9A CN115981689A (en) | 2022-12-26 | 2022-12-26 | Method for realizing arranging and upgrading based on component version number field analysis strategy |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211675061.9A CN115981689A (en) | 2022-12-26 | 2022-12-26 | Method for realizing arranging and upgrading based on component version number field analysis strategy |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115981689A true CN115981689A (en) | 2023-04-18 |
Family
ID=85959080
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211675061.9A Pending CN115981689A (en) | 2022-12-26 | 2022-12-26 | Method for realizing arranging and upgrading based on component version number field analysis strategy |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115981689A (en) |
-
2022
- 2022-12-26 CN CN202211675061.9A patent/CN115981689A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7356816B2 (en) | Method and apparatus for multiplatform migration | |
| KR101105177B1 (en) | Data container for user interface content data | |
| US7367027B1 (en) | System for generating efficient and compact update packages | |
| CN102622241B (en) | A kind of method for upgrading software and device | |
| EP0938050A2 (en) | Modular storage method and apparatus for use with software applications | |
| WO2001061470A2 (en) | Method and apparatus for multiplatform migration | |
| CN1886976B (en) | Method and apparatus for performing actions on a wireless device using action lists and versioning | |
| CN109375922A (en) | A kind of automatic generation method and terminal device of interface document | |
| CN106775623A (en) | Plan the processing method and processing device of allocation list | |
| CN102567053A (en) | Method and device for downgrading software version | |
| CN111160045A (en) | Game resource file translation method, device and equipment | |
| US20120290596A1 (en) | Stabilized binary differencing | |
| CN106843984A (en) | The update method and device of application database | |
| CN102025548B (en) | Multi-version smooth upgrading method and device for user-defined performance indexes | |
| CN111488483B (en) | Method, device, terminal and non-transitory computer readable storage medium for updating a library | |
| US6592628B1 (en) | Modular storage method and apparatus for use with software applications | |
| US11029934B2 (en) | Method and system for updating legacy software | |
| US20060048140A1 (en) | Method, system and article for generating installation merge packages | |
| US8924676B1 (en) | Efficient storage load redistribution | |
| CN115981689A (en) | Method for realizing arranging and upgrading based on component version number field analysis strategy | |
| US20030084031A1 (en) | System and method for searching a signature set for a target signature | |
| CN114756276A (en) | Software version control method based on baseline | |
| CN108833128A (en) | A kind of method that equipment updates | |
| CN113694532A (en) | Method, system, storage medium and terminal for resource reuse in resource manager | |
| CN111124413B (en) | Method and device for compiling Maven project |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Building 9, No. 186 Heyang Road, High tech Industrial Development Zone, Zhengzhou City, Henan Province, 450001 Applicant after: Zhengzhou Yunzhi Xin'an Security Technology Co.,Ltd. Address before: 450001 Floor 3, Building A, Building 2, No. 186 Heyang Road, Zhengzhou Hi tech Industrial Development Zone, Henan Province Applicant before: Zhengzhou Yunzhi Xin'an Security Technology Co.,Ltd. |
|
| CB02 | Change of applicant information |