Installation package generation method, device, equipment and storage medium

Abstract

The disclosure provides a kind of installation package generation method, installation package generation device, electronic equipment and non-transient computer readable storage medium, it is related to computer field, especially in the field of application promotion technology.The specific implementation scheme is: obtaining original code data;Wherein, original code data includes basic code data and difference code data;Difference code data includes the difference code logic under different release channels that meets corresponding release strategy;The difference code logic of each release channel is packed with basic code data respectively, and the to-be-released installation package of corresponding release channel is generated.According to the technology of the present disclosure, the packing efficiency of the to-be-released installation package under multiple release channels is improved, and code maintenance is facilitated.

Description

Technical Field

[0001] This disclosure relates to the field of computers, and more particularly to the field of application promotion technology, specifically to an installation package generation method, an installation package generation device, an electronic device, and a non-transitory computer-readable storage medium. Background Technology

[0002] With the continuous development of internet technology, smartphones, tablets, and other terminal devices have become increasingly common. These devices typically provide users with corresponding functional services through applications. To increase user adoption, application installation packages are usually distributed through various channels for users to download and use. Summary of the Invention

[0003] This disclosure provides an installation package generation method, an installation package generation apparatus, an electronic device, and a non-transitory computer-readable storage medium.

[0004] According to one aspect of this disclosure, a method for generating an installation package is provided, comprising:

[0005] Obtain raw code data; wherein, the raw code data includes basic code data and differential code data; the differential code data includes differential code logic that meets the corresponding release strategies under different release channels;

[0006] The different code logic for each release channel is packaged with the basic code data to generate the corresponding release channel's installation package.

[0007] According to another aspect of this disclosure, an electronic device is also provided, comprising:

[0008] At least one processor; and

[0009] A memory communicatively connected to the at least one processor; wherein,

[0010] The memory stores instructions that can be executed by the at least one processor, which, when executed, enables the at least one processor to perform any of the installation package generation methods provided in the embodiments of this disclosure.

[0011] According to another aspect of this disclosure, a non-transitory computer-readable storage medium storing computer instructions is also provided, wherein the computer instructions are used to cause a computer to execute any of the installation package generation methods provided in the embodiments of this disclosure.

[0012] The technology disclosed herein improves the packaging efficiency of installation packages to be released under multiple distribution channels and facilitates code maintenance.

[0013] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0014] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0015] Figure 1 This is a flowchart of an installation package generation method provided in an embodiment of this disclosure;

[0016] Figure 2 This is a flowchart of another method for generating an installation package provided in this embodiment of the disclosure;

[0017] Figure 3 This is a structural diagram of an installation package generation apparatus provided in an embodiment of this disclosure;

[0018] Figure 4 This is a block diagram of an electronic device used to implement the installation package generation method of the embodiments of this disclosure. Detailed Implementation

[0019] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0020] The installation package generation methods and apparatuses provided in this disclosure are applicable to application scenarios where installation packages of the same application are distributed through different distribution channels. The installation package generation methods provided in the embodiments of this disclosure can be executed by an installation package generation apparatus, which can be implemented in software and / or hardware and specifically configured in an electronic device.

[0021] To facilitate understanding, the method for generating the installation package will be explained in detail first.

[0022] See Figure 1 The method for generating an installation package, as shown, includes:

[0023] S101. Obtain the original code data; wherein, the original code data includes basic code data and differential code data; the differential code data includes differential code logic that meets the corresponding release strategy under different release channels.

[0024] The original code data includes the original code logic corresponding to the application that can be released through different channels. By packaging the original code logic corresponding to different release channels, the installation package to be released for the corresponding release channel can be obtained.

[0025] The original code data includes basic code data, which characterizes the business logic of the application to implement its business functions; and differential code data, which characterizes the differential code logic that meets the corresponding release strategies under different release channels. A release channel can be understood as a platform that provides the application installation package for users to download. A release strategy refers to the restrictions and rules that the installation package must adhere to when provided on a release channel. For example, some release channels prohibit applications with application distribution functions from being listed.

[0026] It should be noted that since different distribution channels usually have personalized distribution strategies, the original code data is enriched and made more comprehensive by including the difference code logic that matches the distribution strategies of different distribution channels in the original code data, thus providing data support for the subsequent generation of installation packages for different distribution channels.

[0027] For example, the raw code data can be pre-stored on the local machine of the execution device corresponding to the installation package generation method, on other storage devices associated with the execution device, or in the cloud, and the raw code data can be retrieved from the corresponding storage space when the installation package needs to be generated.

[0028] In one optional embodiment, the difference code data can be generated according to the release strategy dimension. For example, the difference code logic of each release strategy can be combined to obtain the difference code data; the difference code logic of each release strategy is marked with the release channel that is adapted to the corresponding release strategy.

[0029] It should be noted that when different release channels all need to meet the same release strategy, the difference code logic for that release strategy needs to mark each release channel that is compatible with that release strategy. Therefore, each release strategy must mark at least one release channel.

[0030] For example, for each release strategy's corresponding differential code logic, a channel identifier for the release channel adapted to that release strategy can be added to the differential code logic. By using the channel identifier and the release strategy of the tagged differential code logic, a correspondence between the release channel and the release strategy is established, thus facilitating the subsequent acquisition of differential code logic for different release channels. The channel identifier uniquely identifies the release channel; for example, it can be a channel name or channel number.

[0031] It is understandable that generating differential code data according to the release strategy dimension can avoid the duplication of differential code logic corresponding to the same release strategy, thereby reducing the amount of differential code data.

[0032] In another optional embodiment, the difference code data can be generated according to the release channel dimension. For example, the difference code logic of the release channels can be combined to obtain difference code data for different release channels; wherein, the difference code logic of each release channel consists of the difference code logic of the release strategy adapted to the corresponding release channel.

[0033] For example, for each release channel, the differential code logic is combined according to the differential code logic corresponding to each release strategy under that release channel to obtain the differential code logic corresponding to that release channel; the differential code logic of different release channels is combined to obtain differential code data.

[0034] It is understandable that generating difference code data according to the release channel makes it easier to find and obtain the difference code logic of different release channels, which helps to improve the efficiency of generating subsequent installation packages for different release channels.

[0035] S102. Package the difference code logic of each release channel with the basic code data to generate the corresponding release channel's installation package.

[0036] For each distribution channel, the application installation package is packaged according to the differences in code logic and basic code data for that channel to obtain an application installation package adapted to the distribution channel's distribution strategy; this application installation package is then used as the release package. Furthermore, after generating the release package, the corresponding release package can be automatically published on that distribution channel; or, in response to a publication operation, the corresponding release package can be published on that distribution channel.

[0037] This disclosure introduces raw code data including basic code data and differential code data. Since the differential code data includes differential code logic that meets the corresponding release strategies for different release channels, the richness and comprehensiveness of the code logic carried by the raw code data are improved. This eliminates the need for separate code data maintenance for different release channels, thus improving the convenience of code maintenance. By packaging the differential code logic for each release channel separately with the basic code data to generate the corresponding release-ready installation package, it is possible to simultaneously generate release-ready installation packages adapted to different release channels, improving the packaging efficiency of release-ready installation packages.

[0038] Based on the above technical solutions, this disclosure also provides an optional embodiment. In this embodiment, the repackaging mechanism for updating the original code data is described in detail. It should be noted that for parts not described in detail in the embodiments of this disclosure, please refer to the relevant descriptions in the foregoing embodiments.

[0039] See Figure 2 The method for generating an installation package, as shown, includes:

[0040] S201. Obtain the original code data; the original code data includes basic code data and differential code data; the differential code data includes the differential code logic that meets the corresponding release strategy under different release channels.

[0041] S202. Package the difference code logic of each release channel with the basic code data to generate the corresponding release channel's installation package.

[0042] S203. In response to code logic editing operations, update the original code data.

[0043] The code logic editing operation can include at least one of the following: adding, deleting, and modifying code logic in the original code data.

[0044] Optionally, code logic editing operations may include basic code editing operations to indicate updates to the basic code data in the original code data. Alternatively, code logic editing operations may include strategy change operations to indicate updates to the difference code data in the original code data.

[0045] In one alternative embodiment, the base code data in the original code data is updated in response to the base code editing operation.

[0046] For example, if an application needs to update some business functions (such as adding, deleting, or optimizing some business functions), the application will add, delete, or optimize the business code logic related to the business functions to be updated in the basic code data of the original code data accordingly.

[0047] In another alternative embodiment, in response to a policy change operation, the differential code logic of the changed policy in the differential code data is updated.

[0048] For example, if the release channel updates the release strategy (such as adding, deleting, or modifying the release strategy), the difference code logic associated with the updated release strategy in the difference code data in the original code data will be added, deleted, or optimized accordingly.

[0049] S204. Take the difference code logic of each release channel in the updated original code data and repackage it with the basic code data in the updated original code data to generate the corresponding release channel's installation package.

[0050] For each distribution channel, the application installation package is repackaged based on the differences in code logic and basic code data for that distribution channel in the updated original code data to obtain a new application installation package adapted to the distribution channel's distribution strategy; this new application installation package is then used as the release package. Furthermore, after generating the release package, the corresponding release package can be automatically republished on that distribution channel, or, in response to a distribution operation, the corresponding release package can be republished on that distribution channel.

[0051] In an optional embodiment, if the updated code is the basic code data in the original code data, the difference code logic for each release channel is repackaged with the updated basic code data to generate the corresponding release channel's installation package.

[0052] Understandably, the above technical solution can adapt to the updates of the basic code data in the original code data and regenerate the installation packages to be released for different distribution channels. It eliminates the need to maintain multiple versions of code data in different original code data for different distribution channels, thereby improving the convenience of code maintenance and increasing the efficiency of generating installation packages to be released when the code logic is updated.

[0053] In another optional embodiment, if the updated code is the difference code logic in the original code data, then the associated release channel corresponding to the difference code logic of the changed strategy is determined; the difference code logic of each associated release channel in the updated difference code data is repackaged with the basic code data to generate the release package to be installed for the corresponding associated release channel.

[0054] This embodiment of the disclosure determines the associated release channels when updating the difference code logic in the original code data, and generates a new installation package to be released only for the determined associated release channels. Compared with the method of repackaging each release channel in the updated original code data, this reduces the amount of computation caused by repackaging channels with unchanged release strategies, saves computing resources, and improves repackaging efficiency.

[0055] For example, if the original code data is generated by combining data according to the release strategy dimension, the release channel marked in the difference code logic of the changed strategy can be used as the associated release channel. If the original code data is generated by combining data according to the release channel dimension, the release channel to which the difference code logic of the changed strategy belongs can be directly used as the associated release channel.

[0056] Understandably, the above technical solution can determine the associated release channels for raw code data generated from different dimensions, thereby increasing the richness of the methods for determining associated release channels, laying the foundation for the generation of different raw code data, and helping to improve the compatibility of the installation package generation method.

[0057] For example, for each associated release channel, the updated difference code data for that associated release channel is repackaged with the basic code data to generate a new application installation package for that associated release channel; this new application installation package is then used as the installation package to be released.

[0058] This disclosure allows for the maintenance of only one set of original code data when the original code data is updated, which improves the convenience of code data maintenance compared to the prior art that maintains a separate set of original code data for different distribution channels. Furthermore, after updating the original code data, this disclosure directly repackages the basic code data within the updated original code data, thereby generating installation packages for different distribution channels and improving the convenience and efficiency of repackaging.

[0059] As an implementation of the above-described methods for generating installation packages, this disclosure also provides an optional embodiment of an execution apparatus for implementing the above-described methods for generating installation packages. See further details. Figure 3 The installation package generation device 300 shown includes: a raw code data acquisition module 301 and a packaging module 302. Among them,

[0060] The original code data acquisition module 301 is used to acquire original code data; wherein, the original code data includes basic code data and differential code data; the differential code data includes differential code logic that meets the corresponding release strategies under different release channels;

[0061] The packaging module 302 is used to package the difference code logic of each release channel with the basic code data to generate the corresponding release channel's installation package.

[0062] This disclosure introduces raw code data including basic code data and differential code data. Since the differential code data includes differential code logic that meets the corresponding release strategies for different release channels, the richness and comprehensiveness of the code logic carried by the raw code data are improved. This eliminates the need for separate code data maintenance for different release channels, thus improving the convenience of code maintenance. By packaging the differential code logic for each release channel separately with the basic code data to generate the corresponding release-ready installation package, it is possible to simultaneously generate release-ready installation packages adapted to different release channels, improving the packaging efficiency of release-ready installation packages.

[0063] In an optional embodiment, the installation package generation apparatus 300 further includes:

[0064] The first difference code data generation module is used to combine the difference code logic of each release strategy to obtain difference code data.

[0065] The different code logic for each release strategy is marked with the release channel that is adapted to the corresponding release strategy.

[0066] In an optional embodiment, the installation package generation apparatus 300 further includes:

[0067] The second difference code data generation module is used to combine the difference codes of various release channels to obtain difference code data for different release channels.

[0068] The differential code logic for each release channel consists of the differential code logic for each release strategy adapted to the corresponding release channel.

[0069] In an optional embodiment, the installation package generation apparatus 300 further includes:

[0070] The edit operation response module is used to update the original code data in response to code logic editing operations;

[0071] The repackaging module is used to repackage the different code logic for each release channel in the updated original code data with the basic code data in the updated original code data, and generate the corresponding release package for the release channel.

[0072] In an optional embodiment, the edit operation response module includes:

[0073] The first response unit is used to respond to basic code editing operations and update the basic code data in the original code data;

[0074] Repackage the module, including:

[0075] The first repackaging unit is used to repackage the different code logic for each release channel with the updated basic code data to generate the corresponding release channel's installation package.

[0076] In an optional embodiment, the edit operation response module includes:

[0077] The second response unit is used to update the difference code logic of the changed policy in the difference code data in response to the policy change operation;

[0078] Repackage the module, including:

[0079] The associated release channel determination unit is used to determine the associated release channels corresponding to the difference code logic of the changed strategy;

[0080] The second repackaging unit is used to repackage the difference code logic of each associated release channel in the updated difference code data with the basic code data to generate the corresponding release channel's installation package.

[0081] In one optional embodiment, the associated publishing channel determination unit includes:

[0082] The first channel identification sub-unit is used to associate the release channel marked in the difference code logic of the changed strategy as the associated release channel; or,

[0083] The second channel determines the sub-unit, which is used to identify the release channel to which the difference code logic of the changed strategy belongs as the associated release channel.

[0084] The above-described installation package generation apparatus can execute the installation package generation method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects for executing each installation package generation method.

[0085] The collection, storage, use, processing, transmission, provision, and disclosure of the original code data involved in this technical solution comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0086] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0087] Figure 4 A schematic block diagram of an example electronic device 400 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0088] like Figure 4As shown, device 400 includes a computing unit 401, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 402 or a computer program loaded from storage unit 408 into random access memory (RAM) 403. RAM 403 may also store various programs and data required for the operation of device 400. The computing unit 401, ROM 402, and RAM 403 are interconnected via bus 404. Input / output (I / O) interface 405 is also connected to bus 404.

[0089] Multiple components in device 400 are connected to I / O interface 405, including: input unit 406, such as keyboard, mouse, etc.; output unit 407, such as various types of monitors, speakers, etc.; storage unit 408, such as disk, optical disk, etc.; and communication unit 409, such as network card, modem, wireless transceiver, etc. Communication unit 409 allows device 400 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0090] The computing unit 401 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 401 performs the various methods and processes described above, such as the installation package generation method. For example, in some embodiments, the installation package generation method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 408. In some embodiments, part or all of the computer program may be loaded and / or installed onto device 400 via ROM 402 and / or communication unit 409. When the computer program is loaded into RAM 403 and executed by the computing unit 401, one or more steps of the installation package generation method described above may be performed. Alternatively, in other embodiments, the computing unit 401 may be configured to perform the installation package generation method by any other suitable means (e.g., by means of firmware).

[0091] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0092] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0093] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0094] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0095] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0096] Computer systems can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is established by computer programs running on the respective computers and having a client-server relationship with each other. A server can be a cloud server, also known as a cloud computing server or cloud host, a hosting product within the cloud computing service ecosystem that addresses the management difficulties and weak business scalability inherent in traditional physical hosting and VPS services. Servers can also be servers for distributed systems or servers integrated with blockchain technology.

[0097] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution provided in this disclosure can be achieved, and this is not limited herein.

[0098] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for generating an installation package, comprising: Obtain raw code data; wherein, the raw code data includes basic code data and differential code data; the differential code data includes differential code logic that meets the corresponding release strategies under different release channels; the basic code data is used to characterize the business code logic of the application to implement its business functions; the differential code data is generated according to the release strategy dimension; The different code logic for each release channel is packaged with the basic code data to generate the corresponding release channel's installation package; The difference code data is generated in the following manner: The difference code logic of each release strategy is combined to obtain the difference code data; wherein, the difference code logic of each release strategy is marked with the release channel adapted to the corresponding release strategy; or, The differential code logic of each release channel is combined to obtain the differential code data of different release channels; wherein, the differential code logic of each release channel is composed of the differential code logic of each release strategy adapted to the corresponding release channel.

2. The installation package generation method according to claim 1 further includes: In response to code logic editing operations, update the original code data; The different code logic for each release channel in the updated original code data is repackaged with the basic code data in the updated original code data to generate the corresponding release package for each release channel.

3. The installation package generation method according to claim 2, wherein, The process of updating the original code data in response to code logic editing operations includes: In response to a basic code editing operation, update the basic code data in the original code data; The step of repackaging the difference code logic for each distribution channel in the updated original code data with the basic code data in the updated original code data to generate the corresponding release package for each distribution channel includes: The different code logic for each of the aforementioned release channels is repackaged with the updated basic code data to generate the corresponding release channel's installation package.

4. The installation package generation method according to claim 2, wherein, The process of updating the original code data in response to code logic editing operations includes: In response to a policy change operation, update the differential code logic of the changed policy in the differential code data; The step of repackaging the difference code logic for each distribution channel in the updated original code data with the basic code data in the updated original code data to generate the corresponding release package for each distribution channel includes: Identify the associated release channels corresponding to the differing code logic of the changed strategy; The updated difference code data for each associated release channel is repackaged with the basic code data to generate the corresponding release package for each associated release channel.

5. The installation package generation method according to claim 4, wherein, The associated publishing channels corresponding to the differential code logic of the changed strategy include: Use the release channels marked in the difference code logic of the changed strategy as the associated release channels; or, The release channel to which the difference code logic of the changed strategy belongs is designated as the associated release channel.

6. An installation package generation apparatus, comprising: The raw code data acquisition module is used to acquire raw code data; wherein, the raw code data includes basic code data and differential code data; the differential code data includes differential code logic that meets the corresponding release strategies under different release channels; the basic code data is used to characterize the business code logic of the application to implement its business functions; the differential code data is generated according to the release strategy dimension; The packaging module is used to package the different code logic of each release channel with the basic code data to generate the corresponding release channel's installation package; The first difference code data generation module is used to combine the difference code logic of each release strategy to obtain the difference code data; wherein, the difference code logic of each release strategy is marked with the release channel that is adapted to the corresponding release strategy; The second differential code data generation module is used to combine the differential code logic of each release channel to obtain the differential code data of different release channels; wherein, the differential code logic of each release channel is composed of the differential code logic of each release strategy adapted to the corresponding release channel.

7. The installation package generation apparatus according to claim 6, further comprising: The edit operation response module is used to update the original code data in response to code logic editing operations; The repackaging module is used to repackage the different code logic for each release channel in the updated original code data with the basic code data in the updated original code data, and generate the corresponding release package for the release channel.

8. The installation package generation apparatus according to claim 7, wherein, The editing operation response module includes: The first response unit is used to update the basic code data in the original code data in response to the basic code editing operation; The repackaging module includes: The first repackaging unit is used to repackage the difference code logic of each of the aforementioned release channels with the updated basic code data to generate the release package to be installed for the corresponding release channel.

9. The installation package generation apparatus according to claim 7, wherein, The editing operation response module includes: The second response unit is used to update the difference code logic of the changed policy in the difference code data in response to the policy change operation. The repackaging module includes: The associated release channel determination unit is used to determine the associated release channels corresponding to the difference code logic of the changed strategy. The second repackaging unit is used to repackage the difference code logic of each associated release channel in the updated difference code data with the basic code data to generate the corresponding associated release channel's installation package.

10. The installation package generation apparatus according to claim 9, wherein, The associated publishing channel determination unit includes: The first channel identification subunit is used to associate the release channel marked in the difference code logic of the changed strategy as the associated release channel; or, The second channel determines the sub-unit, which is used to identify the release channel to which the difference code logic of the changed strategy belongs as the associated release channel.

11. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the installation package generation method according to any one of claims 1-5.

12. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to execute the installation package generation method according to any one of claims 1-5.

13. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the installation package generation method according to any one of claims 1-5.

Images