Software installation package manufacturing method and device, electronic equipment and storage medium

Abstract

The invention provides a software installation package manufacturing method and device, electronic equipment and a storage medium, and relates to the technical field related to databases, the method comprises the steps that a plurality of installation entry class files are configured in an installation script corresponding to a to-be-manufactured software installation package, a target software package is generated, each entry class file corresponds to one installation command type, and the installation entry class files correspond to one installation command type; the target software package is suitable for software installation modes corresponding to various installation command types, so that an installation script in the target software is configured with installation entry classes corresponding to different installation command types, and installation logics defined by the installation entry classes can be executed; the installation packages of different installation types are integrated in one target software package, the problem that multiple installation packages need to be generated through repeated compiling in the software package manufacturing process is solved, the manufacturing efficiency of the software packages is improved, the number of provided installation package versions is reduced, and the management efficiency of the software installation packages is improved.

Description

Technical Field

[0001] This invention relates to the field of database-related technologies, specifically to a method, apparatus, electronic device, and storage medium for creating software installation packages. Background Technology

[0002] Due to the inherent differences in the Linux operating system environment, it is often necessary to provide installation packages suitable for different environments when installing software.

[0003] In related technologies, a separate installation package is created for each environment. Each creation requires recompiling and repackaging, which takes more time and results in low efficiency in software installation package creation. Furthermore, the creation of multiple different versions of the installation package increases the complexity of software management. Summary of the Invention

[0004] In view of this, it is necessary to provide a method, apparatus, electronic device and storage medium for creating software installation packages to solve the technical problems of low efficiency in creating software installation packages and inconvenience in software management in the prior art.

[0005] To address the aforementioned technical problems, in a first aspect, the present invention provides a method for creating a software installation package, comprising: Configure multiple installation entry class files in the installation script corresponding to the software installation package to be created, and generate the target software package. Each entry class file corresponds to an installation command type, so that the target software package is applicable to software installation methods corresponding to multiple installation command types.

[0006] In one possible implementation, the installation command type includes at least a first type corresponding to command-line installation, a second type corresponding to graphical installation, and a third type corresponding to silent installation; the installation entry class file includes a command-line installation entry class, a graphical installation entry class, and a silent installation entry class; configuring multiple installation entry class files in the installation script corresponding to the software installation package to be created includes: Write the command-line installation entry class corresponding to the first type into the installation script; Write the graphical installation entry class corresponding to the second type into the installation script; Write the silent installation entry class corresponding to the third type into the installation script.

[0007] In one possible implementation, the installation script includes a silent installation entry class corresponding to the third type, comprising: Obtain the Java class file corresponding to the silent installation entry class, wherein the Java class file is used to parse the XML format configuration file corresponding to the silent installation entry class; The Java class file is written into the installation script to generate the silent installation entry class.

[0008] In one possible implementation, after configuring multiple installation entry class files in the installation script corresponding to the software installation package to be created and generating the target software package, the method further includes: Upon receiving the software package to be installed, the package is extracted to a temporary directory of the system to be installed. Enter the temporary directory, parse the command-line parameters of the software installation command input by the user, and obtain the parsing result; When the parsing result is of the first type, the command-line installation entry class is selected from the target software package as the current entry class; Execute the current entry class to implement package installation via command line.

[0009] One possible implementation also includes: When the parsing result is the second type, the graphical installation entry class is selected from the target software package as the current entry class; The current entry class is executed to implement package installation in a graphical manner.

[0010] One possible implementation also includes: When the parsing result is the third type, obtain the path of the configuration file corresponding to the silent installation entry class; The path is passed into the silent installation entry class to obtain the target installation entry class; The target installation entry class is executed to read the configuration information of the configuration file, thereby enabling silent package installation.

[0011] One possible implementation also includes: Delete the temporary directory.

[0012] Secondly, the present invention also provides a software installation package creation apparatus, comprising: The production unit is used to configure multiple installation entry class files in the installation script corresponding to the software installation package to be produced, and generate the target software package. Each entry class file corresponds to an installation command type, so that the target software package is applicable to software installation methods corresponding to multiple installation command types.

[0013] Thirdly, the present invention also provides an electronic device, including a memory and a processor, wherein the memory is used to store a program; The processor, coupled to the memory, is used to execute the program stored in the memory to implement the steps in the software installation package creation method described in any of the above implementations.

[0014] Fourthly, the present invention also provides a computer-readable storage medium for storing a computer-readable program or instruction, which, when executed by a processor, can implement the steps in the software installation package creation method described in any of the above implementations.

[0015] The beneficial effects of this invention are: The software installation package creation method provided by this invention generates a target software package by configuring multiple installation entry class files in the installation script corresponding to the software installation package to be created. Each entry class file corresponds to an installation command type, so that the target software package is applicable to software installation methods corresponding to multiple installation command types. This allows the installation script in the target software to be configured with installation entry classes corresponding to different installation command types, thereby enabling the execution of the installation logic defined by each installation entry class. This achieves the technical effect of "one target software package, multiple installation methods," integrating installation packages of different installation types into one target software package. It solves the problem of repeatedly compiling and generating multiple installation packages during the software package creation process, improves the efficiency of software package creation, reduces the number of provided installation package versions, and improves the management efficiency of software installation packages. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 A schematic flowchart of an embodiment of the software installation package creation method provided by the present invention; Figure 2 For the present invention Figure 1 A schematic diagram of an embodiment of S101; Figure 3 For the present invention Figure 2 A schematic diagram of an embodiment of S203; Figure 4 A schematic diagram of an embodiment of the software installation package creation apparatus provided by the present invention; Figure 5 A schematic diagram of an embodiment of the electronic device provided by the present invention. Detailed Implementation

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0019] In the description of the embodiments of the present invention, unless otherwise stated, "multiple" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0020] The terms "first," "second," etc., used in the embodiments of this invention are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a technical feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature.

[0021] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0022] The execution subject of the software installation package creation method in this application embodiment can be the software installation package creation device provided in this application embodiment, or different types of electronic devices such as server equipment, physical host, or user equipment (UE) that integrate the software installation package creation device. The software installation package creation device can be implemented in hardware or software. The UE can specifically be a terminal device such as a smartphone, tablet computer, laptop computer, handheld computer, desktop computer, or personal digital assistant (PDA).

[0023] This invention provides a method, apparatus, electronic device, and storage medium for creating software installation packages, which will be described below.

[0024] Figure 1 A schematic flowchart of an embodiment of the software installation package creation method provided by the present invention is shown below. Figure 1 As shown, the methods for creating software installation packages include: S101. Configure multiple installation entry class files in the installation script corresponding to the software installation package to be created, and generate the target software package. Each entry class file corresponds to an installation command type, so that the target software package is applicable to software installation methods corresponding to multiple installation command types.

[0025] The software installation package to be created refers to the software installation package that needs to be created to be compatible with different Linux operating systems with different installation command types. The target package refers to the software installation package configured with multiple installation entry point files in the installation script.

[0026] Installation scripts are executable scripts (usually POSIX shell scripts) embedded in the target software package, such as shell scripts.

[0027] Installation entry point files are class files that exist in bytecode form within the target software package and each contains a program entry method (such as Java's public static void main(String[] args)). Each entry point file uniquely corresponds to one type of installation command.

[0028] Specifically, multiple installation entry class files are configured in the installation script corresponding to the software installation package to be created, generating the target software package. Each entry class file corresponds to an installation command type, making the target software package suitable for software installation methods corresponding to various installation command types. This allows the installation script in the target software to be configured with installation entry classes corresponding to different installation command types, enabling each to execute the installation logic defined by the installation entry class. This achieves the technical effect of "one target software package, multiple installation methods," integrating installation packages of different installation types into one target software package. It solves the problem of repeatedly compiling and generating multiple installation packages during the software package creation process, improves the efficiency of software package creation, reduces the number of provided installation package versions, and improves the management efficiency of software installation packages.

[0029] In summary, the software installation package creation method provided by this invention generates a target software package by configuring multiple installation entry class files in the installation script corresponding to the software installation package to be created. Each entry class file corresponds to an installation command type, making the target software package suitable for software installation methods corresponding to multiple installation command types. This allows the installation script in the target software to be configured with installation entry classes corresponding to different installation command types, enabling each to execute the installation logic defined by its respective entry class. This achieves the technical effect of "one target software package, multiple installation methods," integrating installation packages of different installation types into a single target software package. It solves the problem of repeatedly compiling and generating multiple installation packages during the software package creation process, improves the efficiency of software package creation, reduces the number of provided installation package versions, and enhances the management efficiency of software installation packages.

[0030] In some embodiments of the present invention, the installation command type includes at least a first type corresponding to command-line installation, a second type corresponding to graphical installation, and a third type corresponding to silent installation; the installation entry class file includes a command-line installation entry class, a graphical installation entry class, and a silent installation entry class; such as Figure 2 As shown, step S101 includes: S201. Write the command-line installation entry class corresponding to the first type into the installation script; S202. Write the graphical installation entry class corresponding to the second type into the installation script; S203. Write the silent installation entry class corresponding to the third type into the installation script.

[0031] The installation command types include at least the first type corresponding to command-line installation, the second type corresponding to graphical installation, and the third type corresponding to silent installation.

[0032] Specifically, by configuring the corresponding installation entry class for different installation command types in the same installation script, command-line interactive installation, graphical interface installation, and silent installation can be achieved. Moreover, only one compilation and packaging is required to generate a unique target software package, avoiding the repetitive work of creating independent installation packages for each installation method in traditional solutions, and significantly reducing time, storage, and distribution costs.

[0033] In one specific implementation, multiple installation entry class files are configured in the installation script corresponding to the software installation package to be created. The process of generating the target software package is as follows: First, write the installer. Taking Java as an example, write the installer's JAR file and predefine different installation entry classes according to different installation methods. The entry class for command-line installation is defined as com.install.console.main, the entry class for graphical installation is defined as com.install.graph.main, and the entry class for silent installation is defined as com.install.auto.main.

[0034] Then, write the shell script that needs to be executed during installation, i.e., the installation script. Specifically, write the command-line installation entry class corresponding to the first type in the installation script; write the graphical installation entry class corresponding to the second type in the installation script; and write the silent installation entry class corresponding to the third type in the installation script.

[0035] Finally, the target software package is generated based on the installation script, so that the target software package includes a command-line installation entry class, a graphical installation entry class, and a silent installation entry class.

[0036] In some embodiments of the present invention, such as Figure 3 As shown, step S203 includes: S301. Obtain the Java class file corresponding to the silent installation entry class, wherein the Java class file is used to parse the XML format configuration file corresponding to the silent installation entry class; S302. Write the Java class file into the installation script to generate the silent installation entry class.

[0037] The XML configuration file is a text file written in Extensible Markup Language (XML) for silent installation scenarios, describing the configurable items required for installation. The Java class file is used to parse the XML configuration file to implement silent installation.

[0038] The root element is a characteristic structure in an XML configuration file, which can be... <install>.

[0039] Specifically, a Java class file is written into the installation script to generate the silent installation entry class. This can be a series of parameter nodes arranged sequentially as child elements under the root element. Each parameter node is labeled with its parameter name, and its text content contains the corresponding default value. This allows the default values ​​for each parameter to be written under the root element, generating an XML configuration file for silent installation. The Java class file used to parse this XML configuration file is then written into the installation script, generating the silent installation entry class. This XML configuration file is provided to the user for configuration and subsequent silent installation, improving the efficiency of the silent installation process.

[0040] In one specific implementation, for silent installation, a configuration file predefines default parameter values. The configuration file uses XML to write the default values, with the following specific format: <install> <param1> default1< / param1> <param2> default2< / param2> …… < / install> The root element of the XML is defined as install, and then the names and default values ​​of each parameter are defined.

[0041] In some embodiments of the present invention, after step S101, the method further includes: S401. Upon receiving the software package to be installed, decompress the software package to the temporary directory of the system to be installed; S402. Enter the temporary directory, parse the command line parameters of the software installation command input by the user, and obtain the parsing result; S403. When the parsing result is the first type, select the command-line installation entry class from the target software package as the current entry class; S404. Execute the current entry class to implement package installation via command line.

[0042] Among them, the software package to be installed refers to the software package that needs to be installed.

[0043] Specifically, upon receiving a software package to be installed, the package is extracted to a temporary directory of the system to be installed, so that the system does not need to install additional tools or retain redundant files beforehand. The system enters the temporary directory, parses the command-line parameters of the software installation command input by the user, and obtains the parsing result. If the parsing result is of the first type, the command-line installation entry class is selected from the target software package as the current entry class, and the current entry class is executed to realize the software package installation via command line.

[0044] In some embodiments of the present invention, it further includes: S501. When the parsing result is the second type, select the graphical installation entry class from the target software package as the current entry class; S502. Execute the current entry class to implement package installation in a graphical manner.

[0045] Specifically, when the parsing result is of type 2, the graphical installation entry class is selected from the target software package as the current entry class, and the current entry class is executed to achieve graphical software package installation.

[0046] In some embodiments of the present invention, it further includes: S601. When the parsing result is the third type, obtain the path of the configuration file corresponding to the silent installation entry class; S602. Pass the path into the silent installation entry class to obtain the target installation entry class; S603. Execute the target installation entry class to read the configuration information of the configuration file and implement silent package installation.

[0047] Specifically, when the parsing result is of type three, the path of the configuration file corresponding to the silent installation entry class is obtained and passed to the silent installation entry class so that the silent installation entry class can obtain its corresponding configuration file, generate the target installation entry, and execute the target installation entry class to read the configuration information of the configuration file. This can be achieved by parsing the default values ​​of each parameter to complete the non-interactive installation in one go, thus realizing silent package installation.

[0048] In one specific implementation, the process of installing software packages via command line, graphical interface, or silent method is as follows: First, upon receiving the package to be installed, extract the package to a temporary directory of the system to be installed: tar xvf - -C $tempdir 2> / dev / null; Then, navigate to the temporary directory: cd $tempdir; Different installation entry files are specified depending on the software installation command entered during installation; the default is command-line installation. When the command `. / install.bin -c` is executed, the first input parameter `-c` is retrieved, defining the installation entry class as the command-line installation entry class `com.install.console.main`. When the command `. / install.bin -g` is executed, the first input parameter `-g` is retrieved, defining the installation entry class as the graphical installation entry class `com.install.graph.main`. When the command `. / install.bin -a / path / install.xml` is executed, the first input parameter `-a` is retrieved, defining the installation entry class as the silent installation entry class `com.install.auto.main`, and the second parameter is the path to the silent installation parameter configuration file ` / path / install.xml`. The above steps are defined in the shell script as follows: main_class = "com.install.console.main" if ["X$1" = "Xc" -o "X$1" = "XC"] then main_class = "com.install.console.main" fi if ["X$1" = "Xg" -o "X$1" = "XG"] then main_class = "com.install.graph.main" fi if ["X$1" = "Xa" -o "X$1" = "XA"] then main_class = "com.install.auto.main" fi The installer's entry point class has now been defined. Different commands are executed based on the entry point class. For graphical and command-line installation commands, simply run the installation entry point class file. For silent installation, the path to the parameter configuration file needs to be passed in so that the installer can analyze it before proceeding. The shell script is defined as follows: if ["X$1" = "Xa" -o "X$1" = "XA"] then $java_home / bin / java -classpath $classpath $main_class "$2" else $java_home / bin / java -classpath $classpath $main_class fi In some embodiments of the present invention, it further includes: S701. Delete the temporary directory.

[0049] Specifically, after the software package installation is complete, the temporary directory is deleted to avoid residual files affecting the system to be installed, thus saving disk space and improving the security of software package creation.

[0050] In one specific implementation, the process of compiling software source code is as follows: The compiled code, the installer's JAR file, and the installation script are packaged into a single binary installation file. Users can select the installation method by entering different command parameters, reducing the steps of repeated compilation and packaging, improving the efficiency of software package creation, integrating multiple installation methods into one installation package, simplifying software version management, and allowing users to choose different installation methods according to their needs, including silent installation.

[0051] To better implement the software installation package creation method in this embodiment of the invention, based on the software installation package creation method, correspondingly, such as... Figure 4 As shown, this embodiment of the invention also provides a software installation package creation apparatus, the software installation package creation apparatus 400 comprising: The production unit 401 is used to configure multiple installation entry class files in the installation script corresponding to the software installation package to be produced, and generate a target software package. Each entry class file corresponds to an installation command type, so that the target software package is applicable to software installation methods corresponding to multiple installation command types.

[0052] The software installation package creation apparatus 400 provided in the above embodiments can realize the technical solutions described in the above software installation package creation method embodiments. The specific implementation principles of each module or unit can be found in the corresponding content in the above software installation package creation method embodiments, and will not be repeated here.

[0053] like Figure 5 As shown, the present invention also provides an electronic device 500. The electronic device 500 includes a processor 501, a memory 502, and a display 503. Figure 5 Only some components of the electronic device 500 are shown, but it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented instead.

[0054] In some embodiments, processor 501 may be a central processing unit (CPU), microprocessor, or other data processing chip, used to run program code stored in memory 502 or process data, such as the software installation package creation method of the present invention.

[0055] In some embodiments, processor 501 may be a single server or a group of servers. The server group may be centralized or distributed. In some embodiments, processor 501 may be local or remote. In some embodiments, processor 501 may be implemented on a cloud platform. In one embodiment, the cloud platform may include a private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, inter-cloud, multi-cloud, or any combination thereof.

[0056] In some embodiments, memory 502 may be an internal storage unit of electronic device 500, such as a hard disk or memory of electronic device 500. In other embodiments, memory 502 may also be an external storage device of electronic device 500, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc. equipped on electronic device 500.

[0057] Furthermore, the memory 502 may include both internal storage units of the electronic device 500 and external storage devices. The memory 502 is used to store application software and various types of data installed on the electronic device 500.

[0058] In some embodiments, display 503 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. Display 503 is used to display information from electronic device 500 and to display a visual user interface. Components 501-503 of electronic device 500 communicate with each other via a system bus.

[0059] In one embodiment, when processor 501 executes the software installation package creation program in memory 502, the following steps can be performed: Configure multiple installation entry class files in the installation script corresponding to the software installation package to be created, and generate the target software package. Each entry class file corresponds to an installation command type, so that the target software package is applicable to software installation methods corresponding to multiple installation command types.

[0060] It should be understood that when the processor 501 executes the software installation package creation program in the memory 502, in addition to the functions mentioned above, it can also perform other functions, as detailed in the description of the corresponding method embodiments above.

[0061] Furthermore, this embodiment of the invention does not specifically limit the type of electronic device 500 mentioned. Electronic device 500 can be a mobile phone, tablet computer, personal digital assistant (PDA), wearable device, laptop computer, or other portable electronic device. Exemplary embodiments of portable electronic devices include, but are not limited to, portable electronic devices running iOS, Android, Microsoft, or other operating systems. The aforementioned portable electronic device can also be other portable electronic devices, such as a laptop computer with a touch-sensitive surface (e.g., a touch panel). It should also be understood that in some other embodiments of the invention, electronic device 500 may not be a portable electronic device, but rather a desktop computer with a touch-sensitive surface (e.g., a touch panel).

[0062] Accordingly, this application also provides a computer-readable storage medium for storing computer-readable programs or instructions. When the programs or instructions are executed by a processor, they can implement the steps or functions of the software installation package creation method provided in the above-described method embodiments.

[0063] Those skilled in the art will understand that all or part of the processes of the methods described in the above embodiments can be implemented by a computer program instructing related hardware (such as a processor, controller, etc.), and the computer program can be stored in a computer-readable storage medium. The computer-readable storage medium may be a disk, optical disk, read-only memory, or random access memory, etc.

[0064] The software installation package creation method, apparatus, electronic device, and storage medium provided by the present invention have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.< / install>

Claims

1. A software installation package production method characterized by comprising: The application comprises the following steps: A plurality of installation entry class files are configured in an installation script corresponding to a software installation package to be made, and a target software package is generated, wherein each entry class file corresponds to an installation command type, so that the target software package is applicable to software installation modes corresponding to a plurality of installation command types.

2. The software installation package production method according to Claim 1, characterized by, The installation command types at least include a first type corresponding to a command line installation mode, a second type corresponding to a graphical installation mode, and a third type corresponding to a silent installation mode, and the installation entry class files include a command line installation entry class, a graphical installation entry class, and a silent installation entry class. The step of configuring a plurality of installation entry class files in the installation script corresponding to the software installation package to be made comprises the following steps: A command line installation entry class corresponding to the first type is written in the installation script. A graphical installation entry class corresponding to the second type is written in the installation script. A silent installation entry class corresponding to the third type is written in the installation script.

3. The software installation package production method according to Claim 2, characterized by, The step of writing the silent installation entry class corresponding to the third type in the installation script comprises the following steps: A Java class file corresponding to the silent installation entry class is obtained, wherein the Java class file is used to parse an XML format configuration file corresponding to the silent installation entry class. The Java class file is written in the installation script to generate the silent installation entry class.

4. The software installation package production method according to Claim 2, characterized by, After the step of configuring a plurality of installation entry class files in the installation script corresponding to the software installation package to be made to generate the target software package, the following steps are further included: When a software package to be installed is received, the software package is decompressed into a temporary directory of a system to be installed. Command line parameter analysis is performed on a software installation command input by a user in the temporary directory to obtain an analysis result. When the analysis result is the first type, the command line installation entry class is selected from the target software package as a current entry class. The current entry class is executed to implement software package installation in a command line mode.

5. The software installation package production method according to Claim 3, characterized by, The following steps are further included: When the analysis result is the second type, the graphical installation entry class is selected from the target software package as a current entry class. The current entry class is executed to implement software package installation in a graphical mode.

6. The software installation package production method according to Claim 4, characterized by, The following steps are further included: When the analysis result is the third type, a path of a configuration file corresponding to the silent installation entry class is obtained. The path is transmitted into the silent installation entry class to obtain a target installation entry class. The target installation entry class is executed to read configuration information of the configuration file, and software package installation in a silent mode is implemented.

7. The software package production method according to any one of claims 4 to 6, wherein The following step is further included: The temporary directory is deleted.

8. A software installation package creating apparatus characterized by comprising: The application comprises the following steps: A production unit is configured to configure a plurality of installation entry class files in an installation script corresponding to a software installation package to be made, and a target software package is generated, wherein each entry class file corresponds to an installation command type, so that the target software package is applicable to software installation modes corresponding to a plurality of installation command types.

9. An electronic device, comprising: The application comprises a memory and a processor, wherein the memory is used to store a program. The processor is coupled with the memory and used to execute the program stored in the memory to realize the steps in the software package manufacturing method of any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, A computer readable program or instruction is stored, and the program or instruction is executed by a processor to realize the steps in the software package manufacturing method of any one of claims 1 to 7.

Images