CN111679855A - Application software package conversion method, management method and device - Google Patents

Application software package conversion method, management method and device Download PDF

Info

Publication number
CN111679855A
CN111679855A CN202010798439.9A CN202010798439A CN111679855A CN 111679855 A CN111679855 A CN 111679855A CN 202010798439 A CN202010798439 A CN 202010798439A CN 111679855 A CN111679855 A CN 111679855A
Authority
CN
China
Prior art keywords
software package
format
software
application
package
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
Application number
CN202010798439.9A
Other languages
Chinese (zh)
Inventor
符兴斌
鲁振
胡坚升
程志斌
李锁在
韩鹏
吴正好
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chinasoft Information System Engineering Co ltd
Original Assignee
Chinasoft Information System Engineering Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Chinasoft Information System Engineering Co ltd filed Critical Chinasoft Information System Engineering Co ltd
Priority to CN202010798439.9A priority Critical patent/CN111679855A/en
Publication of CN111679855A publication Critical patent/CN111679855A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/76Adapting program code to run in a different environment; Porting
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Abstract

The embodiment of the application provides an application program software package conversion method, a management method and a device, wherein the software package conversion method comprises the following steps: confirming that the acquired software package belongs to a software package to be converted, wherein the software package to be converted comprises a software package based on an RPM (revolution speed) format or a software package based on a DEB (digital object bus) format; extracting production information from the software package, wherein the production information comprises an operation file, a control file and dependency information; and manufacturing a target software package according to the manufacturing information, wherein the target software package carries a uniform software authentication identification number. Some embodiments of the application provide a method for converting software packages in RPM and DEB formats into target software packages in a common format, and can solve the compatibility problem of application software packages of operating systems of domestic computers.

Description

Application software package conversion method, management method and device
Technical Field
The embodiment of the application relates to the field of application software package management, in particular to an application software package conversion method, an application software package management method and an application software package management device.
Background
With the rapid maturity of the operating system of the domestic computer, the application software of the domestic computer is developed vigorously in the related industry field, and the domestic operating system is mostly customized and developed based on an open source Unix/Linux kernel. Due to the problems of inconsistent image sources of an operating system, diversified versions of a software development kit, non-uniform management of an application software package and the like in the objective fragmentation of open-source Linux, the management of the application software of a domestic computer system faces huge challenges.
The management of the application software of the operating system of the domestic computer generally comprises two stages of development and operation of the application software. The application software development stage generally consists of the processes of developing languages, developing libraries, developing, compiling, releasing and the like; the application software running phase generally consists of software installation, upgrading, running and other processes.
At present, the operating systems of the domestic computers have two major mainstream series, namely RedHat series and Debian series.
The package format of the application software package adopted by the RedHat series mainstream is as follows: RPM Package (i.e., Red-Hat Package software Package), the command to install the RPM Package is: "rpm-parameter", corresponding to the package management tool yum, supports tar packages. The package format of the application software package adopted by the main stream of the Debian series is as follows: the DEB package (namely the Debian software package) has a command of 'dpkg-parameter' for installing the DEB package, and the corresponding package management tool is apt-get and supports tar package. yum and apt-get use a central warehouse (relocation) to manage the mutual relation of the application programs, and carry out the related operations such as upgrading, installing, deleting and the like according to the calculated software dependence relation, thus reducing the problem of dependence (dependencies) of the Linux user on headache all the time.
At present, a domestic computer operating system has two major main flow series, namely a RedHat series and a Debian series, and RPM (rotating speed limit) adopted by the two main flow series operating systems is incompatible with DEB (hierarchical object class) format application software, so that the domestic computer application software is not uniformly developed and is incompatible in installation, upgrading and operation.
Disclosure of Invention
Some embodiments of the present application provide a method and an apparatus for managing an os package compatible with multiple formats (e.g., RPM and DEB formats), so as to solve the problem of compatibility of the os package in a home computer.
In a first aspect, some embodiments of the present application provide a software package conversion method, including: confirming that the acquired software package belongs to a software package to be converted, wherein the software package to be converted comprises a software package based on an RPM (revolution speed) format or a software package based on a DEB (digital object bus) format; extracting production information from the software package, wherein the production information comprises an operation file, a control file and dependency information; and manufacturing a target software package according to the manufacturing information, wherein the target software package carries a uniform software authentication identification number.
Some embodiments of the application provide a method for converting software packages in RPM and DEB formats into target software packages in a common format, and can solve the compatibility problem of application software packages of operating systems of domestic computers.
In some embodiments, the object software package comprises a CPK software package, and the producing the object software package according to the production information comprises: setting an authentication identification number of the application software; setting software runtime dependencies of the application software; and manufacturing the CPK software package according to the authentication identification number and the software running dependence.
Some embodiments of the application rely on the manufactured CPK software package when the manufactured software package carries the authentication identification number and the software runs, and can solve the problems of unified authentication management and running environment of application software.
In some embodiments, said extracting production information from said software package comprises: analyzing the software package to be converted; and extracting the operating file, the control file and the dependency information from the analyzed software package.
Some embodiments of the present application complete the production of the software package in the target format by parsing and obtaining the relevant information of the software package to be converted.
In some embodiments, said producing the target software package according to the production information includes: and converting at least part of the production information into the target software package format in a mapping mode.
According to some embodiments of the application, the format of the software package to be converted is converted into the target software package in a mapping mode, so that the compatibility problem of the application software package of the operating system of the domestic computer is solved.
In some embodiments, after the producing the target software package according to the production information, the method further comprises: and issuing the target software package.
Some embodiments of the present application facilitate end-user installation of applications by publishing software packages in a target format.
In some embodiments, before the creating the target software package according to the creation information, the software package conversion method further includes: and acquiring the authentication identification number.
Some embodiments of the application further facilitate management of the application package by the management end by obtaining the unified software authentication identification number of the application from the software package management end.
In a second aspect, an embodiment of the present application provides an application package management method, where the method includes: generating an authentication identification number in response to an application developer request; providing the authentication token number to the application developer; providing a software package format conversion tool to the application developer, wherein the software package format conversion tool is configured to convert a software package format to be converted into a target software package of a uniform format, and the software package format to be converted comprises an RPM format or a DEB format.
In some embodiments, the application package management method further comprises: providing an application helper component to a user terminal of the application, wherein the application helper component is configured to perform an automatic installation of the application in response to an automatic deployment command or is configured to complete an on-demand installation of the application in response to a user input operation.
In a third aspect, some embodiments of the present application provide a software package conversion apparatus, including: the confirming module is configured to confirm that the acquired software package belongs to a software package to be converted, wherein the software package to be converted comprises a software package based on an RPM (revolution speed) format or a software package based on a DEB (digital object class) format; an extraction module configured to extract production information from the software package, wherein the production information includes an operation file, a control file, and dependency information; and the manufacturing module is configured to manufacture the target software package according to the manufacturing information, wherein the target software package carries a uniform software authentication identification number.
In a fourth aspect, some embodiments of the present application provide a software package management apparatus, the apparatus comprising: a generation module configured to generate an authentication identification number in response to an application developer request; and the providing module is configured to provide the authentication identification number for an application developer and provide a software package format conversion tool for the application developer, wherein the software package format conversion tool is configured to convert a software package format to be converted into a target software package in a unified format, and the software package format to be converted comprises an RPM (revolution speed) format or a DEB (digital object bus) format.
In a fifth aspect, some embodiments of the present application provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, may implement the method of the first or second aspect.
In a sixth aspect, some embodiments of the present application provide an information processing apparatus comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor, when executing the program, may implement the method of the first or second aspect.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a flowchart of a software package conversion method provided in an embodiment of the present application;
FIG. 2 is a flowchart of another software package conversion method provided in the embodiments of the present application;
FIG. 3 is a flowchart of a software package management method according to an embodiment of the present application;
fig. 4 is a block diagram illustrating a software package creation apparatus according to an embodiment of the present disclosure;
fig. 5 is a block diagram illustrating a software package management apparatus according to an embodiment of the present disclosure;
fig. 6 is a block diagram of an information processing apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Aiming at the problems of incompatibility of software packages of domestic operating systems and the like, some embodiments of the application provide an operating system software package management method and device compatible with RPM and DEB formats, and the method and device are used for solving the problems of compatibility and visual operation of application software packages of domestic computer operating systems. That is, some embodiments of the present application propose a CPK packet format using APPID as an authentication identifier, and the RPM packet format and the DEB packet format are compatible; a CPK packet management method taking APPID as a trust chain is provided, and RedHat series and Debian series packet conversion is realized.
Some embodiments of the application can realize the conversion of the RedHat series RPM package and the Debian series DEB package through the CPK package standard, meet the unified management of the application software of the operating system of the domestic computer, and improve the use efficiency of the management of the development, installation, upgrading and the like of the application software of the operating system of the domestic computer.
Referring to fig. 1, fig. 1 provides a software package conversion method for some embodiments of the present application, the method including: s101, confirming that the acquired software package belongs to a software package to be converted, wherein the software package to be converted comprises a software package based on an RPM (revolution speed counter) format or a software package based on a DEB (digital object class) format; s102, extracting production information from the software package, wherein the production information comprises an operation file, a control file and dependency information; s103, manufacturing a target software package according to the manufacturing information, wherein the target software package carries a uniform software authentication identification number. Some embodiments of the application provide a method for converting software packages in RPM and DEB formats into target software packages in a common format, and can solve the compatibility problem of application software packages of operating systems of domestic computers.
In some embodiments, S103 the object software package comprises a CPK software package, and the creating the object software package according to the creation information comprises: setting an authentication identification number of the application software; setting software runtime dependencies of the application software; and manufacturing the CPK software package according to the authentication identification number and the software running dependence.
The format of the CPK package is briefly described below and an example of converting RPM and DEB formatted packages to CPK packages is briefly described. For the content of the CPK package format, reference may be made to the application document with publication number "CN 105787299A".
The data in the CPK software package is divided into 2 parts: package data (various types of original data including application software include executable files, configuration files, pictures and the like), description information (basic information including application software, script files of installation/uninstallation/upgrade processes, file lists of the whole CPK software package and the like), and the internal file directory structure design of the CPK software package is shown in table 1 as the internal file directory structure design of the CPK software package:
TABLE 1 design of internal file directory structure of CPK software package
Figure 825172DEST_PATH_IMAGE001
In order to improve the basic information of the externally accessed CPK software package, the basic information of the CPK software package is stored into the control.xml file by using the common XML format standard, and the node design of the content of the control.xml file is shown in "table 2 control.xml file design":
TABLE 2 control. xml document design
Figure 604909DEST_PATH_IMAGE002
Figure 813168DEST_PATH_IMAGE003
Figure 627540DEST_PATH_IMAGE004
Figure 450003DEST_PATH_IMAGE005
In order to ensure that the application software can be normally installed, uninstalled, upgraded and downgraded, all control scripts are integrated into one script control file: and setting a control script in a corresponding position in the file according to actual needs, wherein the design of the install script file is shown in a table 3.
Table 3. install File design
Figure 589472DEST_PATH_IMAGE006
In order to improve the retrieval of the files of the whole CPK software package, all the files and the directories of the CPK software package are stored into a file list file: the file comprises a file, wherein each line of the file records basic information of one file, and the data format of each line is shown in table 4 file design.
Table 4 filelist file design
Figure 788373DEST_PATH_IMAGE007
To accomplish the format conversion of the software package in RPM format or the software package in DEB format to the above CPK software package, in some embodiments, S102 includes: analyzing the software package to be converted; and extracting the operating file, the control file and the dependency information from the analyzed software package. S103 includes: and converting at least part of the production information into the target software package format in a mapping mode.
The packet format standard of the CPK software package according to some embodiments of the present application is as shown in the above table and the corresponding text description, and the CPK software package adopts a uniform internal structure. The packet data and the packet information of the CPK software package are independently stored, and the data and the description information of the CPK software package are completely independently and separately stored. And performing secondary encryption compression on data of the CPK software package, independently compressing the separately stored software package data and software description information respectively, and performing secondary encryption compression on the compressed package to obtain the CPK software package.
For example, the production information extracted from the software package in the RPM format and the software package in the DEB format (for example, the production information includes various types of raw data of the application software including executable files, configuration files, pictures, basic information of the application software, script files of the installation/uninstallation/upgrade process, file list of the entire CPK software package, and the like) is divided into 2 parts: package data (each type of raw data including application software includes executable files, configuration files, pictures, etc.) and description information (including basic information of the application software, script files of the installation/uninstallation/upgrade process, file list of the entire CPK software package, etc.). Storing basic information of application software extracted from a software package in an RPM (revolution speed) format and a software package in a DEB (digital object class) format into a control, XML (extensible markup language) file by adopting a universal XML format standard; integrating script files for extracting installation/uninstallation/upgrade processes from software packages in RPM format and software packages in DEB format into a script control file: install, etc.
In some embodiments, after the producing the target software package according to the production information, the method further comprises: and issuing the target software package. Some embodiments of the present application facilitate end-user installation of applications by publishing software packages in a target format.
In some embodiments, before the creating the target software package according to the creation information, the software package conversion method further includes: and acquiring the authentication identification number. Some embodiments of the application further facilitate management of the application package by the management end by obtaining a uniform software authentication mark number of the application from the software package management end.
The following describes an exemplary application software package conversion method by taking the target software package as a software package in the CPK format in conjunction with fig. 2.
As shown in fig. 2, the method for converting the application software package includes determining that the software package belongs to an RPM format, analyzing the RPM package format, extracting an operation file, extracting a control file, and extracting dependency information; judging that the format of the software package belongs to a DEB format, analyzing the DEB format software package, extracting an operation file, extracting a control file and extracting dependence information; acquiring an authentication identification number of the application software, and setting identification information of the application software according to the authentication identification number; setting software runtime dependencies; and manufacturing a CPK application software package to obtain the manufactured CPK application software package.
Specifically, the software package conversion method of some embodiments of the present application includes:
step 1, confirming that the received software package belongs to the software package in the RPM or DEB format and extracting relevant information in the packages, wherein the relevant information comprises an operation file, a control file and dependency information.
And 2, the application developer sets the application software APPID identification according to the APPID number (namely the authentication identification number) acquired from the operator. For example, the application developer may write this APPID number to the set identification bit. As an example, the operator encrypts the software name and the developer user ID sent by the developer to generate the APPID, and records the APPID in a database. For example, an application developer writes an APPID to a CPK software package using a unified tool, submitting the application to the carrier. And then the operator analyzes the received CPK software package, decrypts the APPID and checks whether the APPID is effective, and if the APPID is effective, the application software enters the next audit.
And step 3: and setting CCF software runtime dependence. For example, the software runtime defines the minimal environment required to run the application in a sandbox (including the necessary library functions for software running and the compiler or compilation engine, etc.) and the APIs (application program interfaces) that communicate with other parts of the system outside the sandbox. Setting the CCF software runtime dependency is to set environment dependency information of the CCF software runtime, for example, information such as the type and version number of the operating platform on which the application software is running, and library information (general library and basic library) required by the runtime.
And 4, step 4: and manufacturing a software package in the CPK format according to the CPK package format.
For the format of the software package in the CPK format, reference may be made to patent application with patent publication number "CN 105787299A," entitled "CPK software package conversion method with security identifier," and the foregoing description also refers to the related description, so that redundant description is not repeated here. The process of making the CPK package may include: the RPM packet format is converted into the CPK packet format by one-to-one mapping, supplementing the difference, deleting the unnecessary content, and the like. Taking the RPM packet format as an example, the process of making the CPK packet may include: and (3) corresponding the relevant information in the RPM software package extracted in the step (1) to a corresponding part in the CPK software package, wherein the content which is possessed by the CPK software package but not possessed by the RPM software package can be completed in a supplementary mode. That is, the RMP packet (or DEB packet) is converted into the CPK software packet in a one-to-one mapping and adding missing information.
And 5: and releasing the CPK software package generated in the step 4).
Step 6: and (6) ending.
It should be noted that, the package management toolset (CpkTools) for the CPK software package may include: the system comprises an application management tool cpkg, an application installation tool cget, an application packaging tool cpkpack and an application transformation tool cpkttransform.
It can be seen that the process of using the application software by the application terminal is as follows: the application software in the whole ecosystem is finally installed, uninstalled and upgraded through the application assistant, and the application assistant runs on each application service terminal PC. The specific installation process may include: automatic installation, after the application assistant runs, if the application service sub-center issues an automatic deployment instruction, the application assistant needs to automatically install application software (application software of a public level); or the user logs in the application assistant and executes the operations of installation, uninstallation, upgrade and startup on the software in the current application assistant according to the actual requirement.
As shown in fig. 3, an embodiment of the present application provides an application package management method, where the method includes: s201, generating an authentication identification number in response to a request of an application program developer; s202, providing the authentication mark number for the application program developer; s203, providing a software package format conversion tool for the application program developer, wherein the software package format conversion tool is configured to convert the format of the software package to be converted into a target software package with a uniform format.
In some embodiments, the application package management method further comprises: providing an application helper component to a user terminal of the application, wherein the application helper component is configured to perform an automatic installation of the application in response to an automatic deployment command or is configured to complete an on-demand installation of the application in response to a user input operation.
Referring to fig. 4, fig. 4 shows a software package conversion device for an application program provided in an embodiment of the present application, it should be understood that the device corresponds to the above-mentioned method embodiment of fig. 1, and is capable of executing various steps related to the above-mentioned method embodiment, and specific functions of the device may be referred to the above description, and detailed descriptions are appropriately omitted herein to avoid repetition. The device comprises at least one software functional module which can be stored in a memory in the form of software or firmware or solidified in an operating system of the device, and the software package manufacturing device comprises: a confirming module 101 configured to confirm that the acquired software package belongs to a software package to be converted, wherein the software package to be converted comprises a software package based on an RPM format or a software package based on a DEB format; an extraction module 102 configured to extract production information from the software package, wherein the production information includes an operation file, a control file, and dependency information; and the making module 103 is configured to make a target software package according to the running information, wherein the target software package carries a uniform software authentication identification number.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus described above may refer to the corresponding process in fig. 1 or fig. 2, and will not be described in detail herein.
Referring to fig. 5, fig. 5 shows a software package management apparatus for an application program according to an embodiment of the present application, it should be understood that the apparatus corresponds to the above-mentioned method embodiment of fig. 3, and is capable of performing various steps related to the above-mentioned method embodiment, and specific functions of the apparatus may be referred to the above description, and detailed descriptions are appropriately omitted herein to avoid repetition. The device comprises at least one software functional module which can be stored in a memory in the form of software or firmware or solidified in an operating system of the device, and the software package management device comprises: a generating module 501 configured to generate an authentication identification number in response to an application developer request; a providing module 502 configured to provide the authentication token number to an application developer and provide a software package format conversion tool to the application developer, wherein the software package format conversion tool is configured to convert a software package format to be converted into a target software package in a unified format.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus described above may refer to the corresponding process in fig. 1 or fig. 2, and will not be described in detail herein.
Some embodiments of the present application provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, may implement the method of fig. 1 or 3.
As shown in fig. 6, some embodiments of the present application provide an information processing apparatus 600, which includes a memory 610, a processor 620, and a computer program stored on the memory 610 and executable on the processor 620, wherein the processor 620 can implement the method of fig. 1 or fig. 3 when reading the program from the memory 610 through a bus 630 and executing the program.
Processor 620 may process digital signals and may include various computing structures. Such as a complex instruction set computer architecture, a structurally reduced instruction set computer architecture, or an architecture that implements a combination of instruction sets. In some examples, processor 620 may be a microprocessor.
Memory 610 may be used to store instructions that are executed by processor 620 or data related to the execution of the instructions. The instructions and/or data may include code for performing some or all of the functions of one or more of the modules described in embodiments of the application. The processor 620 of the disclosed embodiments may be used to execute instructions in the memory 610 to implement the methods shown in fig. 1 or fig. 3. Memory 610 includes dynamic random access memory, static random access memory, flash memory, optical memory, or other memory known to those skilled in the art.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

Claims (12)

1. A method for converting a format of a software package, the method comprising:
confirming that the acquired software package belongs to a software package to be converted, wherein the software package to be converted comprises a software package based on an RPM (revolution speed) format or a software package based on a DEB (digital object bus) format;
extracting production information from the software package, wherein the production information comprises an operation file, a control file and dependency information;
and manufacturing a target software package according to the manufacturing information, wherein the target software package carries a uniform software authentication identification number.
2. The method for converting a format of a software package according to claim 1, wherein the object software package includes a CPK software package, and the creating the object software package based on the creation information includes:
setting the authentication identification number of the application software;
setting software runtime dependencies of the application software;
and manufacturing the CPK software package according to the authentication identification number and the software running dependence.
3. The method of converting a software package format according to claim 1, wherein said extracting production information from said software package comprises:
analyzing the software package to be converted;
and extracting the operating file, the control file and the dependency information from the analyzed software package.
4. The method for converting a format of a software package according to claim 1, wherein the producing a target software package based on the production information includes: and converting at least part of the production information into the format of the target software package in a mapping mode.
5. The method for converting a format of a software package according to claim 1, wherein after the production of the object software package based on the production information, the method further comprises: and issuing the target software package.
6. The package format converting method according to claim 1, wherein before the creating the object package based on the creation information, the package format converting method further comprises: and acquiring the authentication identification number.
7. A method for application package management, the method comprising:
generating an authentication identification number in response to a request of an application developer;
providing the authentication identification number to the application developer;
providing a software package format conversion tool to the application developer, wherein the software package format conversion tool is configured to convert a software package format to be converted into a target software package of a uniform format, and the software package format to be converted comprises an RPM format or a DEB format.
8. The application package management method of claim 7, further comprising: providing an application helper component to a user terminal of the application, wherein the application helper component is configured to perform an automatic installation of the application in response to an automatic deployment command or is configured to complete an on-demand installation of the application in response to a user input operation.
9. A software package converting apparatus, comprising:
the confirming module is configured to confirm that the acquired software package belongs to a software package to be converted, wherein the software package to be converted comprises a software package based on an RPM (revolution speed) format or a software package based on a DEB (digital object class) format;
an extraction module configured to extract production information from the software package, wherein the production information includes an operation file, a control file, and dependency information;
and the manufacturing module is configured to manufacture the target software package according to the manufacturing information, wherein the target software package carries a uniform software authentication identification number.
10. A software package management apparatus, characterized in that the apparatus comprises:
a generation module configured to generate an authentication identification number in response to an application developer request;
and the providing module is configured to provide the authentication identification number for an application developer and provide a software package format conversion tool for the application developer, wherein the software package format conversion tool is configured to convert a software package format to be converted into a target software package in a unified format, and the software package format to be converted comprises an RPM (revolution speed) format or a DEB (digital object bus) format.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 8.
12. An information processing apparatus comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program is operable to implement the method of any one of claims 1 to 8.
CN202010798439.9A 2020-08-11 2020-08-11 Application software package conversion method, management method and device Pending CN111679855A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010798439.9A CN111679855A (en) 2020-08-11 2020-08-11 Application software package conversion method, management method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010798439.9A CN111679855A (en) 2020-08-11 2020-08-11 Application software package conversion method, management method and device

Publications (1)

Publication Number Publication Date
CN111679855A true CN111679855A (en) 2020-09-18

Family

ID=72458193

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010798439.9A Pending CN111679855A (en) 2020-08-11 2020-08-11 Application software package conversion method, management method and device

Country Status (1)

Country Link
CN (1) CN111679855A (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112083951A (en) * 2020-09-24 2020-12-15 中国人民解放军国防科技大学 Software package unified management method and system supporting multiple operating system platforms
CN114706564A (en) * 2022-05-16 2022-07-05 龙芯中科技术股份有限公司 Software package manufacturing method and device, electronic equipment and storage medium
CN112083951B (en) * 2020-09-24 2024-05-14 中国人民解放军国防科技大学 Unified software package management method and system supporting multiple operating system platforms

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103605520A (en) * 2013-11-22 2014-02-26 中标软件有限公司 Rpm software package conversion method and Rpm software package conversion system
CN105787299A (en) * 2015-12-22 2016-07-20 中软信息系统工程有限公司 Method for making cpk software package with security identifier
CN106095514A (en) * 2016-06-22 2016-11-09 深圳市波普安创技术有限公司 The file installation kit of compatible operating system and generation method for down loading thereof
CN106649852A (en) * 2016-12-30 2017-05-10 广州兴森快捷电路科技有限公司 Method and system for converting PCB file into Gerber file
CN108255499A (en) * 2017-07-28 2018-07-06 新华三大数据技术有限公司 component processing method and device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103605520A (en) * 2013-11-22 2014-02-26 中标软件有限公司 Rpm software package conversion method and Rpm software package conversion system
CN105787299A (en) * 2015-12-22 2016-07-20 中软信息系统工程有限公司 Method for making cpk software package with security identifier
CN106095514A (en) * 2016-06-22 2016-11-09 深圳市波普安创技术有限公司 The file installation kit of compatible operating system and generation method for down loading thereof
CN106649852A (en) * 2016-12-30 2017-05-10 广州兴森快捷电路科技有限公司 Method and system for converting PCB file into Gerber file
CN108255499A (en) * 2017-07-28 2018-07-06 新华三大数据技术有限公司 component processing method and device

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112083951A (en) * 2020-09-24 2020-12-15 中国人民解放军国防科技大学 Software package unified management method and system supporting multiple operating system platforms
CN112083951B (en) * 2020-09-24 2024-05-14 中国人民解放军国防科技大学 Unified software package management method and system supporting multiple operating system platforms
CN114706564A (en) * 2022-05-16 2022-07-05 龙芯中科技术股份有限公司 Software package manufacturing method and device, electronic equipment and storage medium
CN114706564B (en) * 2022-05-16 2022-08-30 龙芯中科技术股份有限公司 Software package manufacturing method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
KR100952251B1 (en) Servicing a component base software product
CN100559346C (en) The system and method that is used for instantiating abstract class
KR101795844B1 (en) Runtime system
EP1530127B1 (en) Resource manifest for providing language-neutral and language-specific resource location services
KR100655124B1 (en) Software installation and testing system for a built-to-order computer system
US8181166B2 (en) System and method for determining when an EJB compiler needs to be executed
TWI536263B (en) Projecting native application programming interfaces of an operating system into other programming languages
US9411571B2 (en) Method and apparatus for deploying software as a service
US20060020937A1 (en) System and method for extraction and creation of application meta-information within a software application repository
US8230121B2 (en) Method and apparatus for identifying a device handle in a computer system
US7305376B2 (en) Multiple language-dependent resources compacted into a single resource file
CN103324474B (en) Based on (SuSE) Linux OS across the method for System structure ISO and module
Elrom et al. Neo blockchain and smart contracts
US8224750B1 (en) Method and system for upgrading licenses to installed software
CN112947896B (en) Directed graph-based component dependency analysis method
CN111679855A (en) Application software package conversion method, management method and device
US9244706B2 (en) Command line shell command generation based on schema
WO2011157105A2 (en) Method and device for component expansion
JP5377522B2 (en) Efficiently correlate nominally incompatible types
CN114398102B (en) Application package generation method and device, compiling server and computer readable storage medium
CN106778270B (en) Malicious application detection method and system
CN116991427B (en) Application compiling method and device, computing equipment and storage medium
US8453108B1 (en) Static, configurable kernel interface
US11256602B2 (en) Source code file retrieval
Martin Creating an Operator with Kubebuilder

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
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200918