CN113703787A

CN113703787A - Installation package processing method and device, electronic equipment and computer readable storage medium

Info

Publication number: CN113703787A
Application number: CN202010433269.4A
Authority: CN
Inventors: 潘元森; 胡伟平; 李常坤; 张帅
Original assignee: Qianxin Technology Group Co Ltd; Secworld Information Technology Beijing Co Ltd
Current assignee: Qianxin Technology Group Co Ltd; Secworld Information Technology Beijing Co Ltd
Priority date: 2020-05-20
Filing date: 2020-05-20
Publication date: 2021-11-26

Abstract

The present disclosure provides an installation package processing method, including: embedding a script for analyzing target content to be newly added in the installation package into a rule file of the installation package, wherein the rule file is used for managing the deployment of a target program; newly adding target content at a first target position of the installation package; in the process of deploying the installation package, calling a script to analyze target content; and updating the deployment file of the target program according to the analyzed content. The present disclosure also provides an installation package processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

Description

Installation package processing method and device, electronic equipment and computer readable storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to an installation package processing method, an installation package processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

Background

The software installation package is a collection of files that can be decompressed by itself, including files that are needed at the time of software installation. Once the installation package is manufactured, the content of the installation package is fixed, and the file content and the directory structure which are required to be deployed by the software are determined during packaging. In the process of deploying the installation package, the rule script of the installation package is relied on to perform specified operation at different stages of software management, and the content of the installation package is generally not changed.

However, in an actual application scenario, deployment personnel often need to specify file contents to be deployed according to actual requirements, and particularly, some software with specific configuration needs to be determined only when the software is deployed, so that the configuration files need to be re-modified and re-packaged for each different deployment, and if the configuration contents written during packaging are directly deployed, great difficulty is brought to software deployment. Therefore, in the related art, the complexity of the software deployment mode based on the installation package is high, and the software deployment mode is difficult to adapt to different deployment modes.

Disclosure of Invention

In view of the above, the present disclosure provides an installation package processing method, an installation package processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

One aspect of the present disclosure provides an installation package processing method, including: embedding a script for analyzing target content to be newly added in an installation package into a rule file of the installation package, wherein the rule file is used for managing the deployment of a target program; newly adding the target content at a first target position of the installation package; calling the script to analyze the target content in the process of deploying the installation package; and updating the deployment file of the target program according to the analyzed content.

According to the embodiment of the disclosure, embedding a script for analyzing target content to be newly added in an installation package in a rule file of the installation package comprises: determining a deployment phase in which the installation package is located when the script is executed; and embedding the script into a second target position in a rule file of the installation package according to the deployment phase of the installation package when the script is executed, wherein the second target position corresponds to the deployment phase of the installation package when the script is executed.

According to an embodiment of the present disclosure, adding the target content at the first target location of the installation package includes: and newly adding the target content at the tail of the installation package.

According to an embodiment of the present disclosure, adding the target content at the end of the installation package includes: and adding the target content at the tail of the installation package according to a target format.

According to an embodiment of the present disclosure, adding the target content at the end of the installation package according to the target format includes: performing line feed at the tail of the installation package; and newly adding the target content at the position of the installation package after the line feed at the tail of the installation package.

According to the embodiment of the disclosure, in the process of deploying the installation package, the script is called to analyze the target content: acquiring a storage path of the installation package; searching the installation package according to the storage path of the installation package; and analyzing the target content in the installation package.

Another aspect of the present disclosure provides an installation package processing apparatus including: the device comprises an embedding module, an adding module, a calling module and an updating module.

The embedded module is used for embedding a script for analyzing target content to be newly added in the installation package into a rule file of the installation package, wherein the rule file is used for managing the deployment of a target program;

the adding module is used for adding the target content at a first target position of the installation package;

the calling module is used for calling the script to analyze the target content in the process of deploying the installation package; and

and the updating module is used for updating the deployment file of the target program according to the analyzed content.

Another aspect of the present disclosure provides an electronic device including: one or more processors; memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.

Another aspect of the disclosure provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to implement the method as described above.

Another aspect of the disclosure provides a computer program product comprising executable instructions that, when executed by a processor, cause the processor to implement the method as described above.

According to the embodiment of the present disclosure, by embedding a script for parsing target content to be newly added in an installation package in a rule file for managing deployment of a target program, so that the script can be called to analyze the newly added target content in the process of deploying the installation package, then, the deployment file of the target program is updated according to the analyzed content, so that the software content is dynamically changed by analyzing the newly added content of the installation package during software deployment, the proposal can flexibly realize the modification of the content of the deployment file of the installation package, and can also adapt to various different deployment modes, therefore, the technical problems that the software deployment mode based on the installation package is high in complexity and difficult to adapt to different deployment modes are at least partially overcome, therefore, the technical effects of flexibly modifying the content of the deployment file of the installation package and adapting to various different deployment modes are achieved.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

fig. 1 schematically illustrates an exemplary system architecture to which the installation package processing method and apparatus may be applied, according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow diagram of an installation package processing method according to an embodiment of the disclosure;

FIG. 3 schematically illustrates a flowchart for embedding a script for parsing target content to be added in an installation package in a rule file of the installation package according to an embodiment of the present disclosure;

FIG. 4 is a flow chart that schematically illustrates adding target content in a target format at the end of an installation package, in accordance with an embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow diagram for invoking scripts to parse target content according to an embodiment of the present disclosure;

fig. 6 schematically shows a block diagram of an installation package processing apparatus according to an embodiment of the present disclosure; and

FIG. 7 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method, according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

An embodiment of the present disclosure provides an installation package processing method, including: embedding a script for analyzing target content to be newly added in the installation package into a rule file of the installation package, wherein the rule file is used for managing the deployment of a target program; newly adding target content at a first target position of the installation package; in the process of deploying the installation package, calling a script to analyze target content; and updating the deployment file of the target program according to the analyzed content.

Fig. 1 schematically illustrates an exemplary system architecture 100 to which the installation package processing method and apparatus may be applied, according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, the system architecture 100 according to this embodiment may include

terminal devices

101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired and/or wireless communication links, and so forth.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like.

The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, and/or social platform software, etc. (by way of example only).

The user can use the upper-layer package management tool, such as apt and yum, to indirectly call the lower-layer package management tool, such as dpkg and rpm, to install, update and uninstall the installation package based on the software management modes, such as the application store and the online source, of the

terminal devices

101, 102 and 103. The dpkg, rpm and other bottom layer package management tools are two main package management tools of the linux system operating system at present, and are used for carrying out installation, uninstallation and other operations on an installation package. The realization mechanisms of dpkg and rpm are similar, and the files and directories needing to be installed are packaged into an installation package, and specified operation is carried out at different deployment stages of software management through the rule script of the installation package. Based on the above various package management tools, there may be various different deployment modes, such as: rpm or dpkg, yum or apt, application stores, etc.

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the

terminal devices

101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the installation package processing method provided by the embodiment of the present disclosure may be executed by the

terminal device

101, 102, or 103, or may also be executed by another terminal device different from the

terminal device

101, 102, or 103. Accordingly, the installation package processing apparatus provided by the embodiment of the present disclosure may also be disposed in the

terminal device

101, 102, or 103, or in another terminal device different from the

terminal device

101, 102, or 103.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Fig. 2 schematically shows a flowchart of an installation package processing method according to an embodiment of the present disclosure.

As shown in fig. 2, the method includes operations S210 to S240.

In operation S210, a script for parsing target content to be newly added in the installation package is embedded in a rule file of the installation package, wherein the rule file is used for managing deployment of a target program.

According to embodiments of the present disclosure, the target content may be specific content or rules. The rule file may be used, for example, to deploy service launches and the like after installation of the target program.

In operation S220, target content is newly added to a first target location of the installation package.

According to an embodiment of the present disclosure, the first target location may be a preset location, for example, a target content may be added at the end of the installation package, or a target content may be added at the head of the installation package.

In operation S230, in the process of deploying the installation package, the script is called to parse the target content.

According to the embodiment of the present disclosure, for example, in the case where a specific content or rule is appended to the end of an installation package, the content of a target program is dynamically changed by parsing installation package tail information when the installation package is deployed.

According to the embodiment of the disclosure, taking embedding the shell script in the dpkg or rpm rule file in the linux system as an example, the dpkg or rpm process can embed the shell script when packaging is executed in a specified deployment stage. By embedding the shell script in the installation package rule file, analysis of the additional information of the installation package and modification of the content of the deployment file can be realized in the deployment process.

In operation S240, the deployment file of the target program is updated according to the parsed content.

According to an embodiment of the present disclosure, the deployment file may include at least one of: executable files, configuration files, data files, and the like.

In the related art, once the installation package is manufactured, the content of the installation package is fixed, and the content of the file and the directory structure to be deployed by the software are determined during packaging. In the process of deploying the installation package, the rule script of the installation package is relied on to perform specified operation at different stages of software management, and the content of the installation package is generally not changed.

For example, after the client software is installed, the client software needs to interact with the server immediately when the client software is started for the first time, and since the ip address and the port number of the server are not fixed, only the ip address and the port configuration written in the process of packaging the installation package can be obtained when the client software is installed, so that the server is linked unsuccessfully after the software is installed. Therefore, when the ip address of the server changes, the configuration file must be modified and then repackaged to install the software, and the software deployment complexity is greatly increased. By the embodiment of the disclosure, the ip address and the port configuration of the server can be written into the target position of the installation package, for example, the ip address and the port configuration of the server can be written into the tail of the installation package, during the process of deploying the installation package, a script can be called to analyze the written ip address and the port configuration of the server, and then the configuration file of the target program is updated according to the analyzed content. According to the embodiment of the disclosure, the configuration file of the target program does not need to be modified manually, and the software content can be changed dynamically by analyzing the tail information of the installation package during the deployment of the installation package. Meanwhile, the content which needs to be dynamically changed at different deployment stages of the installation package can be specified when the installation package is deployed.

The method shown in fig. 2 is further described with reference to fig. 3-5 in conjunction with specific embodiments.

Fig. 3 schematically shows a flowchart of embedding a script for parsing target content to be added in an installation package in a rule file of the installation package according to an embodiment of the present disclosure.

As shown in fig. 3, embedding a script for parsing target content to be added in an installation package in a rule file of the installation package includes operations S310 to S320.

In operation S310, a deployment phase in which the script executes the installation package is determined.

In operation S320, the script is embedded into a second target location in the rule file of the installation package according to the deployment phase in which the installation package is located when the script is executed, where the second target location corresponds to the deployment phase in which the installation package is located when the script is executed.

According to the embodiment of the disclosure, when embedding the script, the deployment phase in which the installation package is expected to execute needs to be considered, and then the script is embedded into a different position of the rule file.

Taking a dpkg deployment mode as an example, the deployment stage of the installation package can be divided into four stages: preinst, postestist, prerm and poststrm correspond to the installation package before installation, after installation, before unloading and after unloading respectively. While the rpm deployment mode rule file is slightly more complex, the rule of the installation package is more refined, but four stages are often used: % pre,% post,% preun, and% postun, similar to dpkg, correspond to the four stages before installation, after installation, before unloading, and after unloading. The four stages of dpkg deployment and rpm deployment are specifically worked as shown in table 1.

TABLE 1

According to an embodiment of the present disclosure, for example, the parsing script may be embedded after the files and directories of the installation package are deployed, i.e., in the post phase of dpkg and the% post phase of rpm.

Fig. 4 schematically shows a flowchart of adding target content according to a target format at the end of an installation package according to an embodiment of the present disclosure.

According to the embodiment of the disclosure, the target content can be newly added at the tail of the installation package according to the target format.

As shown in fig. 4, adding the target content according to the target format at the end of the installation package includes operations S410 to S420.

In operation S410, a linefeed is performed at the end of the installation package.

In operation S420, target content is newly added at a position after the line wrapping at the end of the installation package.

According to the embodiment of the present disclosure, the target content may be added in a specified format when added. For example, the specified format may be line feed + apependinfo _ (+ add +), or the specified format may be line feed + apependinfo _ (+ add +) + line feed. The line feed can ensure that the original installation package tail data is not polluted, and can simplify the analysis process of adding the content at the tail.

According to embodiments of the present disclosure, the data parsing script may be invoked after the directory and file release of the installation package.

FIG. 5 schematically shows a flowchart for invoking a script to parse target content according to an embodiment of the present disclosure.

As shown in FIG. 5, parsing the target content with the script during deployment of the installation package includes operations S510-S530.

In operation S510, a storage path of the installation package is acquired.

According to the embodiment of the disclosure, for different deployment modes, different modes can be adopted to obtain the storage path of the installation package. For example, the rpm/dpkg command directly installs the local installation package, the parent process of the current process is the rpm/dpkg process, the rpm/dpkg execution catalog can be obtained through the pwdx command, then the relative catalog of the installation package can be obtained through the rpm/dpkg execution parameters, and the splicing of the two is the absolute path of the installation package. For another example, when yum is used for online installation, the installation package is temporarily stored in a/var/cache/apt/archives directory, and when searching is performed in the directory, the absolute path of the installation package acquired by acquiring the installation package is acquired by performing regular matching by using% (name) and% (version). For another example, when the apt/apt-get online installation is adopted, the temporary storage directory of the installation PACKAGE is/var/cache/apt/archives, and the installation PACKAGE in the cache can be found through environment variables DPKG _ MAINTSCRIPT _ pack (name of installation PACKAGE) and DPKG _ MAINTSCRIPT _ ARCH (architecture) derived in the installation process.

In operation S520, the installation package is searched according to the storage path of the installation package.

In operation S530, the target content in the installation package is parsed.

According to the embodiment of the disclosure, the target content can be read from the installation package and analyzed according to the specified rule. For example, using the regular match "apentinfo _ ()", the target content inside the parentheses is acquired. The target content is data having a predetermined data format.

According to the embodiment of the disclosure, after target content in the installation package is analyzed, the analyzed content can be updated to the deployment file.

Fig. 6 schematically shows a block diagram of an installation package processing apparatus according to an embodiment of the present disclosure.

As shown in fig. 6, the installation package processing apparatus 600 includes: an embedding module 610, an adding module 620, a calling module 630, and an updating module 640.

The embedding module 610 is configured to embed a script for parsing target content to be newly added in the installation package in a rule file of the installation package, where the rule file is used to manage deployment of a target program.

The adding module 620 is used for adding the target content at the first target position of the installation package.

The calling module 630 is configured to call the script to parse the target content in the process of deploying the installation package.

The updating module 640 is configured to update the deployment file of the target program according to the parsed content.

According to an embodiment of the present disclosure, the embedding module 610 is configured to determine a deployment phase in which the installation package is located when the script is executed; and embedding the script into a second target position in a rule file of the installation package according to the deployment phase of the installation package when the script is executed, wherein the second target position corresponds to the deployment phase of the installation package when the script is executed.

According to an embodiment of the present disclosure, the adding module 620 is configured to add the target content at the end of the installation package.

According to an embodiment of the present disclosure, the adding module 620 is configured to add the target content at the end of the installation package according to a target format.

According to an embodiment of the present disclosure, the adding module 620 is configured to perform line feed at the end of the installation package; and newly adding the target content at the position of the installation package after the line feed at the tail of the installation package.

According to an embodiment of the present disclosure, the calling module 630 is configured to obtain a storage path of the installation package; searching the installation package according to the storage path of the installation package; and analyzing the target content in the installation package.

Any of the modules according to embodiments of the present disclosure, or at least part of the functionality of any of them, may be implemented in one module. Any one or more of the modules according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules according to the embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging the circuit, or in any one of three implementations, or in any suitable combination of any of the software, hardware, and firmware. Alternatively, one or more of the modules according to embodiments of the disclosure may be implemented at least partly as computer program modules which, when executed, may perform corresponding functions.

For example, any number of the embedding module 610, the adding module 620, the calling module 630 and the updating module 640 may be combined and implemented in one module/unit/sub-unit, or any one of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the present disclosure, at least one of the embedding module 610, the adding module 620, the calling module 630 and the updating module 640 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware and firmware. Alternatively, at least one of the embedding module 610, the adding module 620, the calling module 630 and the updating module 640 may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.

It should be noted that, the installation package processing apparatus portion in the embodiment of the present disclosure corresponds to the installation package processing method portion in the embodiment of the present disclosure, and the description of the installation package processing apparatus portion specifically refers to the installation package processing method portion, which is not described herein again.

FIG. 7 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method, according to an embodiment of the present disclosure. The computer system illustrated in FIG. 7 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.

As shown in fig. 7, a computer system 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. The processor 701 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 701 may also include on-board memory for caching purposes. The processor 701 may comprise a single processing unit or a plurality of processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 703, various programs and data necessary for the operation of the system 700 are stored. The processor 701, the ROM 702, and the RAM 703 are connected to each other by a bus 704. The processor 701 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 702 and/or the RAM 703. It is noted that the programs may also be stored in one or more memories other than the ROM 702 and RAM 703. The processor 701 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the present disclosure, the system 700 may also include an input/output (I/O) interface 705, the input/output (I/O) interface 705 also being connected to the bus 704. The system 700 may also include one or more of the following components connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program, when executed by the processor 701, performs the above-described functions defined in the system of the embodiment of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 702 and/or the RAM 703 and/or one or more memories other than the ROM 702 and the RAM 703 described above.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. 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 or flowchart illustration, and combinations of blocks in the block diagrams 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. Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. An installation package processing method comprises the following steps:

embedding a script for analyzing target content to be newly added in an installation package into a rule file of the installation package, wherein the rule file is used for managing the deployment of a target program;

newly adding the target content at a first target position of the installation package;

calling the script to analyze the target content in the process of deploying the installation package; and

and updating the deployment file of the target program according to the analyzed content.

2. The method of claim 1, wherein embedding a script in a rule file of an installation package for parsing target content to be added in the installation package comprises:

determining a deployment phase in which the installation package is located when the script is executed; and

and embedding the script into a second target position in a rule file of the installation package according to the deployment phase of the installation package when the script is executed, wherein the second target position corresponds to the deployment phase of the installation package when the script is executed.

3. The method of claim 1, wherein adding the target content at the first target location of the installation package comprises:

and newly adding the target content at the tail of the installation package.

4. The method of claim 3, wherein adding the target content at the end of the installation package comprises:

and adding the target content at the tail of the installation package according to a target format.

5. The method of claim 4, wherein adding the target content in a target format at the end of the installation package comprises:

performing line feed at the tail of the installation package; and

and newly adding the target content at the position of the installation package after the line feed at the tail of the installation package.

6. The method of claim 1, wherein the script is invoked to parse the target content during deployment of the installation package:

acquiring a storage path of the installation package;

searching the installation package according to the storage path of the installation package; and

and analyzing the target content in the installation package.

7. An installation package handling apparatus comprising:

8. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-6.

9. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 6.

10. A computer program product comprising executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 6.