CN105446718B - Method of managing software and system based on red cap software package manager - Google Patents
Method of managing software and system based on red cap software package manager Download PDFInfo
- Publication number
- CN105446718B CN105446718B CN201410409156.5A CN201410409156A CN105446718B CN 105446718 B CN105446718 B CN 105446718B CN 201410409156 A CN201410409156 A CN 201410409156A CN 105446718 B CN105446718 B CN 105446718B
- Authority
- CN
- China
- Prior art keywords
- rpm
- software
- order
- makefile
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The embodiment of the present invention provides a kind of method of managing software and system based on red cap software package manager.Wherein, which comprises obtain the call relation that corresponding RPM order and each RPM order are operated with red cap software package manager RPM；According to the call relation of the RPM order and each RPM order, the generation file Makefile of the RPM operation is generated；The Makefile of the RPM operation, for recording the call relation of the RPM order and each RPM order；The Makefile operated using the RPM, the RPM executed for software are operated.Method of managing software and system provided in an embodiment of the present invention based on red cap software package manager, reduces source code management complexity, improves work efficiency.
Description
Technical field
The present embodiments relate to computer technologies, more particularly to one kind to be based on red cap software package manager (Redhat
Package Manager, abbreviation RPM) method of managing software and system.
Background technique
With the development of computer technology, (SuSE) Linux OS is widely used, and to soft on linux system
The convenience and ease for use of the management of part are more and more by the attention of software developer.
RPM is a kind of for managing the tool for pacifying the operations such as loading, unloading of software on (SuSE) Linux OS.There are five types of RPM
Operation mode is respectively as follows: peace loading, unloading, upgrading, inquiry and verifying, and by using RPM, user voluntarily can install and manage
Software on linux system.
But RPM mechanism provides many orders, to complete RPM and operate the combination needed using multiple orders.Due to life
Enable combination relatively complicated, so that the source code management complexity of existing RPM mechanism is high, low efficiency.
Summary of the invention
The embodiment of the present invention provides a kind of method of managing software and system based on red cap software package manager, solves source code
The problem of management complexity height, low efficiency.
In a first aspect, the embodiment of the present invention provides a kind of method of managing software based on red cap software package manager RPM, institute
The method of stating includes:
Obtain the call relation that corresponding RPM order and each RPM order are operated with RPM；
According to the call relation of the RPM order and each RPM order, the generation file of the RPM operation is generated
Makefile；The Makefile of the RPM operation, for recording the call relation of the RPM order and each RPM order；
The Makefile operated using the RPM, the RPM executed for software are operated.
According in a first aspect, in the first possible implementation of the first aspect, the RPM operation is software patch
Operation is generated, then the Makefile operated using the RPM, the RPM executed for software is operated, comprising:
The Makefile operated using the RPM records the modification content of the software, and generates patch text
Part.
According in a first aspect, in the second possible implementation of the first aspect, the RPM operation be it is following at least
It is a kind of: software installation, software unloading, software upgrading, software inquiry, software verification and software translating.
It is any into second of possible implementation according to the first of first aspect, first aspect,
In the third possible implementation of one side, acquisition RPM order corresponding with RPM operation and each RPM order
Call relation, comprising: obtain and operate the call relation of corresponding node and each node with RPM；The node include with
The RPM operates corresponding RPM order；
The call relation according to the RPM order and each RPM order generates the generation text of the RPM operation
Part Makefile；The Makefile of the RPM operation, the calling for recording the RPM order and each RPM order are closed
System, comprising: according to the node and the call relation of each node, generate the Makefile of the RPM operation；The RPM
The Makefile of operation, for recording the call relation of the node and each node；
The Makefile operated using the RPM, the RPM executed for software are operated, comprising: according to each institute
The call relation of RPM order is stated, each node is called.
Second aspect, the embodiment of the present invention provide a kind of software management system based on red cap software package manager RPM, institute
The system of stating includes:
Module is obtained, for obtaining the call relation for operating corresponding RPM order and each RPM order with RPM；
Generation module generates the RPM operation for the call relation according to the RPM order and each RPM order
Generation file Makefile；The Makefile of RPM operation, for recording the RPM order and each RPM order
Call relation；
Execution module, the Makefile for being operated using the RPM, the RPM executed for software are operated.
According to second aspect, in the first possible implementation of the second aspect, the RPM operation is software patch
Operation is generated, then the execution module is specifically used for the Makefile operated using the RPM, to the modification content of the software
It is recorded, and generates patch file.
According to second aspect, in a second possible implementation of the second aspect, RPM operation be it is following at least
It is a kind of: software installation, software unloading, software upgrading, software inquiry, software verification and software translating.
It is any into second of possible implementation according to the first of second aspect, second aspect,
In the third possible implementation of two aspects, the acquisition module, be specifically used for obtaining corresponding with RPM operation node and
The call relation of each node；The node includes RPM order corresponding with RPM operation；
The generation module generates the RPM behaviour specifically for the call relation according to the node and each node
The Makefile of work；The Makefile of the RPM operation, for recording the call relation of the node and each node；
The execution module calls each node specifically for the call relation according to each RPM order.
Using the method for managing software and system provided in an embodiment of the present invention based on red cap software package manager, pass through by
A series of RPM orders relevant to RPM operation and call relation are encapsulated into Makefile, are operated using Makefile to the RPM
It is managed；When needing to be implemented the RPM operation to software, completes to operate the RPM of software using Makefile, realize
Automatic management reduces source code management complexity, improves work efficiency.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is this hair
Bright some embodiments for those of ordinary skill in the art without any creative labor, can be with
It obtains other drawings based on these drawings.
Fig. 1 is the flow chart of the method for managing software provided in an embodiment of the present invention based on RPM；
Fig. 2 is the structural schematic diagram of the software management system provided in an embodiment of the present invention based on RPM；
Fig. 3 is the schematic illustration of the software management system provided in an embodiment of the present invention based on RPM.
Specific embodiment
In order to make the object, technical scheme and advantages of the embodiment of the invention clearer, below in conjunction with the embodiment of the present invention
In attached drawing, technical scheme in the embodiment of the invention is clearly and completely described, it is clear that described embodiment is
A part of the embodiment of the present invention, instead of all the embodiments.Based on the embodiments of the present invention, those of ordinary skill in the art
Every other embodiment obtained without creative efforts, shall fall within the protection scope of the present invention.
Fig. 1 is the flow chart of the method for managing software provided in an embodiment of the present invention based on RPM.As shown in Figure 1, the side
Method includes:
101, the call relation that corresponding RPM order and each RPM order are operated with RPM is obtained.
102, according to the call relation of the RPM order and each RPM order, the generation text of the RPM operation is generated
Part (Makefile)；The Makefile of the RPM operation, the calling for recording the RPM order and each RPM order are closed
System.
103, the Makefile operated using the RPM, the RPM executed for software are operated.
Optionally, the RPM operation is following at least one: software installation, and software unloads, software upgrading, software inquiry,
Software verification, software translating and software patch generate operation.
Specifically, the executing subject of the method can be the software management system based on RPM.
In existing RPM mechanism, in order to complete some RPM operation for software, need in a certain order, to call
A series of combination of relevant RPM orders is operated to the RPM, and command in combination is relatively complicated.
Method of managing software provided in an embodiment of the present invention based on RPM, will a series of RPMs relevant to RPM operation
Order and call relation are encapsulated into Makefile, are managed using Makefile to RPM operation；It is needing to be implemented to software
The RPM operation when, need to only run generations (make) order, complete to operate the RPM of software using Makefile, realize certainly
Dynamicization management, reduces source code management complexity, improves work efficiency.
It is understood that being operated for any one RPM, such as the unloading of software installation, software, software upgrading, software
Inquiry, software verification, software translating or software patch generate operation, the RPM can be operated a series of RPM being related to
Order and call relation are encapsulated into the Makefile of RPM operation.
In one embodiment, the RPM operation is that software patch generates operation；Correspondingly, the RPM operation
Makefile is used to indicate and records to the modification content of the software, and generates patch file and be packaged.By using soft
Part patch generates the Makefile of operation, modification of the real-time recording needle to software source codes packet, and is made into patch automatically and is packaged, real
Show real-time, the unified management guaranteed the repair free of charge source code and changed, improves the efficiency of source code management.
In another embodiment, one or more nodes are pre-defined；Each node is packaged with one or more RPM lives
It enables, to complete corresponding step or task；Alternatively, the node does not include any RPM order.In practice, it obtains and is grasped with RPM
Make the call relation of corresponding node and each node；The node includes RPM order corresponding with RPM operation；Root
According to the node and the call relation of each node, the Makefile of the RPM operation is generated；The RPM operation
Makefile, for recording the call relation of the node and each node；When being executed, run Makefile, be by
According to the call relation of each RPM order, each node is called.
Fig. 2 is the structural schematic diagram of the software management system provided in an embodiment of the present invention based on RPM.As shown in Fig. 2, this
The software management system 200 based on RPM that inventive embodiments provide, comprising: module 201 is obtained, for obtaining and RPM operation pair
The call relation of the RPM order and each RPM order answered；Generation module 202, for according to the RPM order and it is each described in
The call relation of RPM order generates the generation file Makefile of the RPM operation；The Makefile of the RPM operation, is used
In the call relation for recording the RPM order and each RPM order；Execution module 203, for what is operated using the RPM
Makefile, the RPM executed for software are operated.
Software management system 200 provided in an embodiment of the present invention based on RPM can be used for executing the reality of method shown in Fig. 1
The technical solution of example is applied, it is similar that the realization principle and technical effect are similar, and details are not described herein again.
Optionally, the RPM operation is that software patch generates operation, then the execution module 203 is specifically used for using institute
The Makefile for stating RPM operation, records the modification content of the software, and generate patch file.
Alternatively, optional, the RPM operation is following at least one: software installation, software unloading, software upgrading, software
Inquiry, software verification and software translating.
Optionally, the acquisition module 201 operates corresponding node and each node with RPM specifically for obtaining
Call relation；The node includes RPM order corresponding with RPM operation；
The generation module 202, specifically for the call relation according to the node and each node, described in generation
The Makefile of RPM operation；The Makefile of the RPM operation, the calling for recording the node and each node are closed
System；
The execution module 203 calls each node specifically for the call relation according to each RPM order.
Software management system provided in an embodiment of the present invention based on RPM, will a series of RPMs relevant to RPM operation
Order and call relation are encapsulated into Makefile, are managed using Makefile to RPM operation；It is needing to be implemented to software
The RPM operation when, need to only run generations (make) order, complete to operate the RPM of software using Makefile, realize certainly
Dynamicization management, reduces source code management complexity, improves work efficiency.
Fig. 3 is the schematic illustration of the software management system provided in an embodiment of the present invention based on RPM.As shown in figure 3, this
The software management system 300 based on RPM that inventive embodiments provide, may include such as lower node:
Rpm0 node 301: source code input, such as the source code title for needing to operate.
Srcspec1 node 302: decompression source code packet, and the source code state saved when decompressing are used as memory, so as to subsequent
It operates with.
Rpms1 node 303: compiling source code ultimately generates binary system packet (Binary), if protected in the node operational process
There is original modification information, can according to need and return to original state.
Bb node 304: it is packaged after compiling and generates binary system packet.
Precompile (build) node 305: precompile source code, if preserving original modification letter in the node operational process
Breath, can according to need and return to original state.
Sv node 306: system cache places interim source code.
Save (save) node 307: stored target source code catalogue.
Getchg node 308: modification of the record to source code, and filename can be changed, it automatically saves.
Patch (patch) node 309: intermediate state is retained according to getchg, to source code patch installing.
Ptmp node 310: obtaining from getchg node 308, reconstructs intermediate data so as to a temp directory of packing.
Srcspec2 node 311: compiling source code and be packaged, ultimately generates binary system packet and source code packet.
Ba node 312: it is packaged after compiling and generates binary system packet and source code packet.
Srmps1 node 313: compiling source code ultimately generates source code packet, if preserved original in the node operational process
Modification information can according to need and return to original state.
Bs node 314: it is packaged after compiling and generates source code packet.
Compile (make) node 315: compiling source code.
Install node 316: compiling source code is simultaneously installed, if preserving original modification in the node operational process
Information can according to need and return to original state.
Ph node 317: optional, independent some source code packets.
Above-mentioned node can be predetermined, and each node is packaged with one or more RPM orders, corresponding to complete
The step of or task；When generating the Makefile of some RPM operation, node corresponding with RPM operation and each institute are first obtained
The call relation (sequence) for stating node, according still further to being sequentially generated a Makefile.By taking RPM operation is software installation as an example: complete
It may need to call node 301,302,305,315 and 316 at software installation, obtain between those nodes and those nodes
After call relation, the Makefile of software installation is generated；When being executed, those sections are called according to the Makefile of software installation
Point.Fig. 3 shows the calling principle of each node.Wherein, each node completes the specific process or step of RPM operation, each node
Between be the direction for having flowing.Each node realizes specific process step with program, saves manpower, improves work
Efficiency.
In several embodiments provided by the present invention, it should be understood that disclosed device and method can pass through it
Its mode is realized.For example, the apparatus embodiments described above are merely exemplary, for example, the division of the unit, only
Only a kind of logical function partition, there may be another division manner in actual implementation, such as multiple units or components can be tied
Another system is closed or is desirably integrated into, or some features can be ignored or not executed.Another point, it is shown or discussed
Mutual coupling, direct-coupling or communication connection can be through some interfaces, the INDIRECT COUPLING or logical of device or unit
Letter connection can be electrical property, mechanical or other forms.
The unit as illustrated by the separation member may or may not be physically separated, aobvious as unit
The component shown may or may not be physical unit, it can and it is in one place, or may be distributed over multiple
In network unit.It can select some or all of unit therein according to the actual needs to realize the mesh of this embodiment scheme
's.
It, can also be in addition, the functional units in various embodiments of the present invention may be integrated into one processing unit
It is that each unit physically exists alone, can also be integrated in one unit with two or more units.Above-mentioned integrated list
Member both can take the form of hardware realization, can also realize in the form of hardware adds SFU software functional unit.
The above-mentioned integrated unit being realized in the form of SFU software functional unit can store and computer-readable deposit at one
In storage media.Above-mentioned SFU software functional unit is stored in a storage medium, including some instructions are used so that a computer
It is each that equipment (can be personal computer, server or the network equipment etc.) or processor (processor) execute the present invention
The part steps of embodiment the method.And storage medium above-mentioned includes: USB flash disk, mobile hard disk, read-only memory (Read-
Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic or disk etc. it is various
It can store the medium of program code.
Those skilled in the art can be understood that, for convenience and simplicity of description, only with above-mentioned each functional module
Division progress for example, in practical application, can according to need and above-mentioned function distribution is complete by different functional modules
At the internal structure of device being divided into different functional modules, to complete all or part of the functions described above.On
The specific work process for stating the device of description, can refer to corresponding processes in the foregoing method embodiment, and details are not described herein.
Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention., rather than its limitations；To the greatest extent
Pipe present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that: its according to
So be possible to modify the technical solutions described in the foregoing embodiments, or to some or all of the technical features into
Row equivalent replacement；And these are modified or replaceed, various embodiments of the present invention technology that it does not separate the essence of the corresponding technical solution
The range of scheme.
Claims (8)
1. a kind of method of managing software based on red cap software package manager RPM characterized by comprising
Obtain the call relation that corresponding RPM order and each RPM order are operated with RPM；
According to the call relation of the RPM order and each RPM order, the generation file of the RPM operation is generated
Makefile；The Makefile of the RPM operation, for recording the call relation of the RPM order and each RPM order；
The Makefile operated using the RPM, the RPM executed for software are operated.
2. it is operated the method according to claim 1, wherein the RPM operates to generate for software patch, then it is described
The Makefile operated using the RPM, the RPM executed for software are operated, comprising:
The Makefile operated using the RPM records the modification content of the software, and generates patch file.
3. the method according to claim 1, wherein the RPM operates as following at least one: software installation,
Software unloading, software upgrading, software inquiry, software verification and software translating.
4. method according to claim 1 to 3, which is characterized in that described to obtain RPM order corresponding with RPM operation
And the call relation of each RPM order, comprising: obtain the call relation that corresponding node and each node are operated with RPM；
The node includes RPM order corresponding with RPM operation；
The call relation according to the RPM order and each RPM order generates the generation file of the RPM operation
Makefile；The Makefile of the RPM operation, for recording the call relation of the RPM order and each RPM order,
Include: the call relation according to the node and each node, generates the Makefile of the RPM operation；The RPM operation
Makefile, for recording the call relation of the node and each node；
The Makefile operated using the RPM, the RPM executed for software are operated, comprising: according to each described
The call relation of RPM order calls each node.
5. a kind of software management system based on red cap software package manager RPM, which is characterized in that the system comprises:
Module is obtained, for obtaining the call relation for operating corresponding RPM order and each RPM order with RPM；
Generation module generates the life of the RPM operation for the call relation according to the RPM order and each RPM order
At file Makefile；The Makefile of the RPM operation, for recording the calling of the RPM order and each RPM order
Relationship；
Execution module, the Makefile for being operated using the RPM, the RPM executed for software are operated.
6. system according to claim 5, which is characterized in that the RPM operation is that software patch generates operation, then described
Execution module is specifically used for the Makefile operated using the RPM, records to the modification content of the software, and generate
Patch file.
7. system according to claim 5, which is characterized in that the RPM operation is following at least one: software installation,
Software unloading, software upgrading, software inquiry, software verification and software translating.
8. according to any system of claim 5-7, which is characterized in that
The acquisition module operates the call relation of corresponding node and each node specifically for obtaining with RPM；The section
Point includes RPM order corresponding with RPM operation；
The generation module generates the RPM operation specifically for the call relation according to the node and each node
Makefile；The Makefile of the RPM operation, for recording the call relation of the node and each node；
The execution module calls each node specifically for the call relation according to each RPM order.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410409156.5A CN105446718B (en) | 2014-08-19 | 2014-08-19 | Method of managing software and system based on red cap software package manager |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410409156.5A CN105446718B (en) | 2014-08-19 | 2014-08-19 | Method of managing software and system based on red cap software package manager |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105446718A CN105446718A (en) | 2016-03-30 |
| CN105446718B true CN105446718B (en) | 2019-01-01 |
Family
ID=55556970
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410409156.5A Active CN105446718B (en) | 2014-08-19 | 2014-08-19 | Method of managing software and system based on red cap software package manager |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105446718B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109522202B (en) * | 2017-09-18 | 2022-03-04 | 北京京东尚科信息技术有限公司 | Software testing method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090228881A1 (en) * | 2008-03-04 | 2009-09-10 | Atul Mukker | Linux matrix compilation system and method |
| CN103648116A (en) * | 2013-11-13 | 2014-03-19 | 上海交通大学 | Low-power-consumption wireless-sensor-network optimization method based on program analysis |
-
2014
- 2014-08-19 CN CN201410409156.5A patent/CN105446718B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090228881A1 (en) * | 2008-03-04 | 2009-09-10 | Atul Mukker | Linux matrix compilation system and method |
| CN103648116A (en) * | 2013-11-13 | 2014-03-19 | 上海交通大学 | Low-power-consumption wireless-sensor-network optimization method based on program analysis |
Non-Patent Citations (1)
| Title |
|---|
| "密码算法的随机性测试研究";刘志巍;《中国优秀硕士学位论文全文数据库 信息科技辑》;20110815;第43-51页 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105446718A (en) | 2016-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9489189B2 (en) | Dynamically generate and execute a context-specific patch installation procedure on a computing system | |
| CN110162345B (en) | Application program access method and device and storage medium | |
| US10140355B2 (en) | Compiling extract, transform, and load job test data cases | |
| US10338952B2 (en) | Program execution without the use of bytecode modification or injection | |
| CN106648724B (en) | Application program hot repair method and terminal | |
| CN105574411A (en) | Dynamic unshelling method, device and equipment | |
| CN111090433A (en) | Data processing method, device and storage medium | |
| CN112395039B (en) | Method and device for managing Kubernetes cluster | |
| CN104754032A (en) | Method and device for deploying OpenStack | |
| US20170048331A1 (en) | Platform runtime abstraction | |
| US10705829B2 (en) | Software discovery using exclusion | |
| US20160062754A1 (en) | Coordinating Application Deployment with a Platform Tier | |
| US10884764B1 (en) | Optimizing managed runtime applications for serverless environments | |
| US20180059978A1 (en) | Virtual disk expansion method and apparatus | |
| CN112230857B (en) | Hybrid cloud system, hybrid cloud disk application method and data storage method | |
| US20160224327A1 (en) | Linking a Program with a Software Library | |
| US9436716B2 (en) | Method and system for data plane abstraction to enable a network storage platform ecosystem | |
| US9058576B2 (en) | Multiple project areas in a development environment | |
| CN103309696B (en) | Method and device for updating Java card extended library, and Java card | |
| KR102141749B1 (en) | APP program execution method and device | |
| CN105446718B (en) | Method of managing software and system based on red cap software package manager | |
| CN104506630A (en) | Method, server and system for generating authority data on basis of user roles | |
| WO2023056793A1 (en) | Optimizing a just-in-time compilation process | |
| US11640281B2 (en) | Tool for introspection in object-oriented source code | |
| US10146529B2 (en) | Monitoring rules declaration and automatic configuration of the monitoring rules |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 100095 Building 2, Longxin Industrial Park, Zhongguancun environmental protection technology demonstration park, Haidian District, Beijing Patentee after: Loongson Zhongke Technology Co.,Ltd. Address before: 100095 Building 2, Longxin Industrial Park, Zhongguancun environmental protection technology demonstration park, Haidian District, Beijing Patentee before: LOONGSON TECHNOLOGY Corp.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |