A software source management method, system and medium capable of docking various compilation platforms

Abstract

The application discloses a kind of software source management methods, systems and media that can be docked to multiple compilation platforms, the method of the application includes according to version requirement selecting the target compilation platform required as software package source generation software source development library to obtain development library;From the target compilation platform, update corresponding software package generation time branch;According to the time branch specified in software source warehouse, generate the corresponding time branch in software source controlled library, obtain the controlled library formed by multiple software source controlled libraries;Detection is carried out for the specified time branch, if the specified time branch detection passes, then the specified time branch executes software source release as corresponding software source product library, obtain product library.The application aims to realize a kind of KOJI and OBS etc. compilation platform can be docked to generate software source warehouse and carry out unified, phased, traceable management method, to realize the efficient management, automatic detection and stable release of software source from multiple compilation platforms.

Description

Technical Field

[0001] The present invention relates to the technical field of software source warehouse management, and in particular to a software source management method, system and medium capable of docking with multiple compilation platforms. Background Art

[0002] As software scale and complexity increase, traditional code management and compilation methods are no longer able to meet the demands of modern software development. KOJI and OBS (Open Build Service), commonly used automated compilation platforms, are widely used in communities such as Fedora and OpenSUSE, respectively. However, due to significant differences in usage, the two compilation platforms each have their own shortcomings and deficiencies: KOJI uses tags for management, while OBS uses projects for management; the generated software repository directory structure and storage methods can differ significantly, but publicly available software repositories must be kept consistent to avoid user confusion; KOJI-compiled packages are unsigned; and OBS uses a rolling update process. Even if the package provided to a customer has the same NVR (package name, version, and release) as the current package in the OBS repository, the MD5 may have changed, making it impossible to trace the source; and the package repository generated by OBS for the compilation platform does not include package grouping configuration. In view of this, there is an urgent need for a method that can connect to compilation platforms such as KOJI and OBS to generate software source repositories and conduct unified, phased, and traceable management. Summary of the Invention

[0003] Technical problem to be solved by the present invention: In response to the above-mentioned problems of the prior art, a software source management method, system and medium that can be connected to multiple compilation platforms are provided. The present invention aims to realize a method that can be connected to KOJI and OBS compilation platforms to generate software source warehouses and perform unified, phased and traceable management, so as to achieve efficient management, automatic detection and stable release of software sources from KOJI and OBS compilation platforms.

[0004] In order to solve the above technical problems, the technical solution adopted by the present invention is:

[0005] A software source management method capable of docking with multiple compilation platforms comprises the following steps: S1, selecting a desired target compilation platform as a software package source according to version requirements, completing configuration selection of a software source warehouse, uploading a component definition file of a specified architecture or a general architecture to the software source warehouse, generating a corresponding software source development library according to the software package source, the configuration of the software source warehouse, and the component definition file, thereby obtaining a development library consisting of multiple software source development libraries; S2, after the software source development library is generated, updating the corresponding software package from the target compilation platform into the software source warehouse, generating the latest time branch and warehouse metadata according to the updated current software source information, and retaining the old time branch in the software source warehouse without deleting it; S3, generating a corresponding time branch in a software source controlled library according to the time branch specified in the software source warehouse, thereby obtaining a controlled library consisting of multiple software source controlled libraries; S4, detecting the specified time branch in each software source controlled library in the controlled library, and publishing the software source of the specified time branch as the corresponding software source product library if the specified time branch passes the detection, thereby obtaining a product library consisting of multiple software source product libraries.

[0006] Optionally, when the configuration selection of the software source warehouse is completed in step S1, the target compilation platform includes the KOJI compilation platform or the OBS compilation platform, and the configuration selection of the software source warehouse includes the IP address of the compilation platform, the KOJI label of the KOJI compilation platform, the OBS project of the OBS compilation platform, and part or all of the architecture.

[0007] Optionally, the component definition file of the specified architecture or general architecture in step S1 is saved in the software source warehouse, and if an update of the component definition file is detected, the component definition file in the software source warehouse is automatically updated, wherein the component definition file defines the software package grouping configuration, system installation form configuration and modification history record of the software package in the software source warehouse, wherein the software package grouping configuration is used to support users to install a group of software packages at one time through the group installation command, the system installation form configuration is used to define the display form of the minimal installation and graphical installation of the software package, and the modification history record is used to record the modification history record of the software package.

[0008] Optionally, when updating the corresponding software package from the target compilation platform into the software source warehouse in step S2, the corresponding software package is updated from the target compilation platform into the software source warehouse by using a source package list update or a list screening update.

[0009] Optionally, when generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file in step S1, it includes generating multiple interrelated software source development libraries according to the software package source, the configuration of the software source warehouse and the component definition file at the same time. The multiple software source development libraries are used as the main source and extension source of the software package respectively, and the extension source will be generated in the controlled library together with the main source when the software source controlled library is subsequently generated; and when the software source development library is updated, the software source controlled library is generated in the controlled library according to the default latest time branch or the specified time branch in the main source and the extension source.

[0010] Optionally, step S4 includes:

[0011] S4.1, perform integrity and conflict checks on the specified time branch in the software source controlled library. The integrity check includes scanning and detecting the software packages in the software source controlled library and the software packages in the main source and extended source. If the software package cannot be read, the integrity check fails, or the dependent library is missing, the integrity and conflict checks of the specified time branch are determined to have failed, and the software source cannot be submitted for testing. The process ends and exits. Otherwise, jump to step S4.2.

[0012] S4.2: Extract and analyze the contents of all software packages in the specified time branch in the software source controlled library, categorize them, and generate a software package structure information file appstream.xml. This file is then updated to the software source to provide data support for the operating system graphical interface application store. If the generation of the software package structure information file appstream.xml fails, the process ends and exits; otherwise, it jumps to step S4.3.

[0013] S4.3, if the time branch specified in the software source controlled library is the time branch generated for the first time, jump to step S4.5; otherwise, jump to step S4.4;

[0014] S4.4, for the software packages with the same name between the specified time branch and the previous time branch in the software source controlled library, group them in pairs and perform compatibility testing on the software packages' ABI and KABI. After the testing is complete, all result data is saved and updated to the software source metadata of the controlled library. For the software packages of the specified time branch in the software source controlled library, call the interface to obtain the version-related CVE number and errata information number, generate the corresponding version vulnerability and errata information file updateinfo.xml, and update it to the software source metadata of the controlled library. The CVE number is a unique identifier for a known information security vulnerability or exposure. If the test fails, terminate and exit; otherwise, jump to step S4.5.

[0015] S4.5, perform test operations on the software source controlled library in an automated or manual manner;

[0016] S4.6, if the test operation is passed, the software source executed in the specified time branch is published as the corresponding software source product library, and a product library consisting of multiple software source product libraries is obtained.

[0017] Optionally, after the specified time branch is executed to publish the software source as the corresponding software source product library in step S4, the specified time branch is also included to lock the corresponding time branch of the software source development library in the development library and the corresponding time branch of the software source controlled library in the controlled library, and use the scheduled synchronization task to synchronize the software source of the product library to the external network source to provide software source services to external network users.

[0018] In addition, the present invention also provides a software source management system that can interface with multiple compilation platforms, including a microprocessor and a memory connected to each other, and the microprocessor is programmed or configured to execute the software source management method that can interface with multiple compilation platforms.

[0019] In addition, the present invention also provides a computer-readable storage medium, which stores a computer program or instruction. The computer program or instruction is programmed or configured to execute the software source management method that can be connected to multiple compilation platforms through a processor.

[0020] In addition, the present invention also provides a computer program product, including a computer program or instructions, which are programmed or configured to execute the software source management method capable of docking multiple compilation platforms through a processor.

[0021] Compared with the prior art, the present invention has the following advantages: the method includes selecting the required target compilation platform as the software package source according to the version requirements to generate a software source development library to obtain a development library; updating the corresponding software package generation time branch from the target compilation platform; generating the corresponding time branch in the software source controlled library according to the time branch specified in the software source warehouse, and obtaining a controlled library composed of multiple software source controlled libraries; performing a test on the specified time branch, and if the specified time branch passes the test, publishing the software source executed by the specified time branch as the corresponding software source product library to obtain a product library. The present invention can realize a method that can be connected to compilation platforms such as KOJI and OBS to generate software source warehouses and perform unified, phased, and traceable management, thereby realizing efficient management, automatic detection, and stable release of software sources from multiple compilation platforms. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 Schematic diagram of the basic process of the method of the embodiment of the present invention.

[0023] Figure 2 The figure is a schematic diagram of the composition principle of the software source development library and the software source controlled library in an embodiment of the present invention.

[0024] Figure 3 2 is a flow chart of detecting time branches in an embodiment of the present invention.

[0025] Figure 4 Schematic diagram of the composition principle of the software source product library in an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the technical solution of the present invention, the technical solution of the present invention will be further described in detail below with reference to the accompanying drawings in the embodiments of the present invention.

[0027] like Figure 1 and Figure 2 As shown, the software source management method for connecting to multiple compilation platforms in this embodiment includes the following steps: S1, selecting the required target compilation platform as the software package source according to the version requirement, completing the configuration selection of the software source warehouse, uploading the component definition file of the specified architecture or the general architecture to the software source warehouse, generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file, and obtaining a development library composed of multiple software source development libraries; S2, after the software source development library is generated, updating the corresponding software package from the target compilation platform into the software source warehouse, and generating the latest time branch (for example, Figure 2 20240101-1121 and 20240107-1125 are different time branches) and warehouse metadata (repodata directory), and the old time branches are retained in the software source warehouse without being deleted; S3, generating the corresponding time branch in the software source controlled library according to the time branch specified in the software source warehouse, and obtaining a controlled library composed of multiple software source controlled libraries; S4, detecting the specified time branch in each software source controlled library in the controlled library, and if the specified time branch passes the detection, publishing the software source of the specified time branch as the corresponding software source product library, and obtaining a product library composed of multiple software source product libraries.

[0028] like Figure 2 As shown, when the configuration selection of the software source warehouse is completed in step S1 of this embodiment, the target compilation platform includes the KOJI compilation platform or the OBS compilation platform. In addition, other compilation platforms can be connected as needed. The configuration selection of the software source warehouse includes the IP address of the compilation platform, the KOJI tag (KOJI Tag) of the KOJI compilation platform, the OBS project of the OBS compilation platform, and part or all of the architecture. For example Figure 2 Among them, x86_64 is the X86 architecture, aarch64 is the 64-bit architecture of ARMv8, loongarch64 is the Loongson architecture, etc.

[0029] like Figure 2 As shown, in step S1 of this embodiment, the component definition file for the specified architecture or general architecture is stored in the software source repository. If an update to the component definition file is detected, the component definition file (comps file) in the software source repository is automatically updated. The component definition file defines the package grouping configuration, system installation configuration, and modification history of the software packages in the software source repository. The package grouping configuration supports the user's one-time installation of a group of software packages using the group installation command. For example, after the user configures the software source, they can use the dnf group install command to install the software packages by category. The system installation configuration defines the display modes of the minimal installation and graphical installation of the software packages. The modification history records the modification history of the software packages. This embodiment supports the addition and removal of software source groups and the addition and removal of software packages within the group. When editing the component definition file (comps file), the file is pulled down and data is parsed. After the modification is completed, it is returned to the code repository. This embodiment supports the management of installation modes, including minimal installation, graphical installation, and other modes, through the component definition file (comps file), and supports flexible customization of the mode. The configurable ...

[0030] In step S2 of this embodiment, when updating the corresponding software package from the target compilation platform into the software source warehouse, it includes adopting the source package list update or list screening update method to update the corresponding software package from the target compilation platform into the software source warehouse. By providing two modes of source package list update and list screening update, the corresponding software package can be updated from the corresponding KOJI / OBS compilation platform into the software source development library, making the update more flexible.

[0031] In step S1 of this embodiment, when generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file, it includes generating multiple mutually related software source development libraries according to the software package source, the configuration of the software source warehouse and the component definition file, for example Figure 2It includes four software source warehouses, namely, software source warehouse A to software source warehouse D. The multiple software source development libraries are used as the main source and extended source of the software package respectively. For example, software source warehouse A and software source warehouse D are used as the main sources, and software source warehouse B and software source warehouse C are associated with software source warehouse A and software source warehouse respectively as extended sources; and the extended source will be generated in the controlled library together with the main source when the software source controlled library is subsequently generated; and when the software source development library is updated, the software source controlled library will be generated in the controlled library according to the default latest time branch or the specified time branch in the main source and the extended source. For different development libraries, a certain software source warehouse can be used as the main source, and other software sources can be associated as extended sources. When the software source controlled library is subsequently generated, the extended source will be generated in the controlled library together with the main source. 5. After multiple updates and adjustments in the development library, there are multiple time branches. Select the corresponding main source time branch and extended source time branch (the latest branch by default) to generate the controlled library.

[0032] After the software source controlled library is generated in the warehouse, it still needs to undergo a series of automated detection and supplementary processing, such as Figure 3 As shown, step S4 in this embodiment includes:

[0033] S4.1, perform integrity detection and conflict detection on the time branch specified in the software source controlled library. The integrity detection includes scanning and detecting the software packages in the software source controlled library and the software packages in the main source and extended source. If the software package cannot be read, the integrity check fails, or the dependent library is missing, it is determined that the integrity detection and conflict detection of the specified time branch have failed, and the software source cannot be tested, and the process ends and exits; otherwise, jump to step S4.2; by performing integrity detection and conflict detection on the software source controlled library, ensure that the software packages in the software source are in a usable, reliable, and trustworthy state. Scan and obtain the main source, extended source, and update source of the software source, and integrate them for detection to prevent missing dependencies. If there is a problem with the detection, the corresponding detection report will be returned, and the R&D personnel will manually determine whether to release it or automatically determine whether to release it. After passing the subsequent process, the subsequent process will be executed;

[0034] S4.2: Extract and analyze the contents of all software packages in the specified time branch in the software source controlled library, categorize them, and generate a software package structure information file appstream.xml. This file is then updated to the software source to provide data support for the operating system graphical interface application store. If the generation of the software package structure information file appstream.xml fails, the process ends and exits; otherwise, it jumps to step S4.3.

[0035] S4.3, if the time branch specified in the software source controlled library is the time branch generated for the first time, jump to step S4.5; otherwise, jump to step S4.4;

[0036] S4.4, grouping the software packages with the same name between the specified time branch and the previous time branch in the software source controlled library into pairs and performing compatibility checks on the packages' ABI and KABI. After the checks are complete, all result data is saved and updated to the software source metadata (repodata) of the controlled library. For the software packages (Packages) in the specified time branch in the software source controlled library, calling the interface to obtain the version-related CVE number and errata information number, generating the corresponding version vulnerability and errata information file updateinfo.xml, and updating it to the software source metadata of the controlled library. The CVE number is a unique identifier for a known information security vulnerability or exposure. If the test fails, terminate and exit; otherwise, jump to step S4.5.

[0037] S4.5: Perform automated or manual testing on the controlled library of the software source. In step S4.5, you can perform automated or manual testing on the controlled library. You can view the relationship between the main source and the extended source, the time branch of each development library software source corresponding to the generation of the controlled library, and the change log of the controlled library software package.

[0038] S4.6, if the test operation is passed, the software source executed in the specified time branch is published as the corresponding software source product library, and a product library consisting of multiple software source product libraries is obtained.

[0039] In this embodiment, after the software source of the specified time branch is published as the corresponding software source product library in step S4, the corresponding time branch of the software source development library in the development library and the corresponding time branch of the software source controlled library in the controlled library are locked at the specified time branch, and the software source of the product library is synchronized to the external network source by using the scheduled synchronization task to provide software source services to external network users. Figure 4 As shown, the software source product library in this embodiment includes an os branch, an update branch, and an extension branch. The os branch is used to store software packages in the version generation phase, the update branch is used to store software packages in the version update phase, and the extension branch is used to store warehouse information of the extension source. After the release operation is performed on the controlled library that has passed the test and the corresponding product library is generated, the released software source warehouse will be managed and controlled, and the released version warehouse will be locked and placed in the os branch. Subsequent updates will follow the version update process, and the newly released software packages will be uniformly placed in the update branch for external provision. This embodiment synchronizes the product library software source to the external network source by setting a scheduled synchronization task, and provides software source services to external network users. The method of this embodiment supports viewing the association relationship between the corresponding main source and the extension source, and supports viewing the time branch of the corresponding development library software source when the controlled library is generated.

[0040] To sum up, there is currently no open source complete set of processes from software package compilation to software source warehouse generation, testing, submission for testing and release on the market, and openEuler uses the OBS compilation platform and CentOS uses the KOJI compilation platform, and the usage and structure of the compilation platforms are completely inconsistent. This embodiment can connect to the software source management methods of multiple compilation platforms to integrate the various scattered technologies contained in the process of software package compilation-software source warehouse generation and management-software source verification-software source submission for testing and release, and has made compatible processing for different compilation platforms KOJI and OBS (other compilation platforms can be expanded), and warehouse management is carried out through the form of three-library management. To ensure a better user experience for graphical user interfaces (GUIs), this embodiment uses a script to extract and analyze the contents of all software packages in the controlled software source repository. After unified classification, the generated appstream.xml file is then updated to the software source, providing data support for the operating system's GUI application store. Users can intuitively obtain package descriptions and perform updates in the application store. Currently, operating systems such as OpenEuler and CentOS all provide this service. During the version update phase, this embodiment integrates the software source management method for multiple compilation platforms. Whenever a package is added to the update source, packages with the same name are grouped into pairs and a compatibility check is performed on the ABI and KABI of the packages. After the test is complete, all result data is saved as a compatibility.json file and updated to the controlled repository repodata (software source metadata). This innovative approach utilizes a DNF plug-in package to provide package compatibility test results during DNF package updates. This allows users to easily and clearly understand whether the updated package is compatible with the older version in terms of ABI and KABI during the DNF update phase, ensuring a stable user environment. The method of this embodiment integrates errata information data into the software source during the version update phase, and displays the relevant CVE number (a unique identifier of a known information security vulnerability or exposure) and errata number during the dnf software package update phase. When the user performs a dnf software package update, the corresponding fixed CVE number (a unique identifier of a known information security vulnerability or exposure) is displayed, and the function of updating the software package according to the CVE number or errata number is provided. The software source management method of this embodiment that can be connected to multiple compilation platforms provides a management method for connecting to the KOJI and OBS compilation platforms, and introduces the concepts of development libraries, controlled libraries, and product libraries. Through this method, it is possible to connect to the KOJI and OBS compilation systems to generate a software source warehouse and perform phased and traceable management, thereby achieving the purpose of efficient management, automatic detection, and stable release of software sources.

[0041] In addition, this embodiment also provides a software source management system that can interface with multiple compilation platforms, including a microprocessor and a memory connected to each other, and the microprocessor is programmed or configured to execute the software source management method that can interface with multiple compilation platforms.

[0042] In addition, this embodiment also provides a computer-readable storage medium, which stores a computer program or instruction. The computer program or instruction is programmed or configured to execute the software source management method that can be connected to multiple compilation platforms through a processor.

[0043] In addition, this embodiment also provides a computer program product, including a computer program or instructions, which are programmed or configured to execute the software source management method capable of docking with multiple compilation platforms through a processor.

[0044] Those skilled in the art should understand that the technical solutions provided by the embodiments of the present application may be in the form of methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including the instruction device, which implements the function specified in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the process. Figure 1a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0045] The above description is merely a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiment. All technical solutions based on the concept of the present invention are within the scope of protection of the present invention. It should be noted that for those skilled in the art, various improvements and modifications that do not depart from the principles of the present invention should also be considered within the scope of protection of the present invention.

Claims

1. A software source management method capable of docking with multiple compilation platforms, characterized in that: The method includes the following steps: S1, selecting the required target compilation platform as the source of the software package according to the version requirements, completing the configuration selection of the software source warehouse, uploading the component definition file of the specified architecture or the general architecture to the software source warehouse, generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file, and obtaining a development library composed of multiple software source development libraries; S2, after the software source development library is generated, updating the corresponding software package from the target compilation platform into the software source warehouse, and generating the latest time branch and warehouse metadata according to the updated current software source information, and retaining the old time branch in the software source warehouse without deleting it; S3, generating the corresponding time branch in the software source controlled library according to the time branch specified in the software source warehouse, and obtaining a controlled library composed of multiple software source controlled libraries; S4, detecting the specified time branch in each software source controlled library in the controlled library, and if the specified time branch detection passes, publishing the software source of the specified time branch as the corresponding software source product library, and obtaining a product library composed of multiple software source product libraries; Step S4 includes: S4.1, perform integrity and conflict checks on the specified time branch in the software source controlled library. The integrity check includes scanning and detecting the software packages in the software source controlled library and the software packages in the main source and extended source. If the software package cannot be read, the integrity check fails, or the dependent library is missing, the integrity and conflict checks of the specified time branch are determined to have failed, and the software source cannot be submitted for testing. The process ends and exits. Otherwise, jump to step S4.

2. S4.2: Extract and analyze the contents of all software packages in the specified time branch in the software source controlled library, categorize them, and generate a software package structure information file appstream.xml. This file is then updated to the software source to provide data support for the operating system graphical interface application store. If the generation of the software package structure information file appstream.xml fails, the process ends and exits; otherwise, it jumps to step S4.

3. S4.3, if the time branch specified in the software source controlled library is the time branch generated for the first time, jump to step S4.5; otherwise, jump to step S4.4; S4.4, for the software packages with the same name between the specified time branch and the previous time branch in the software source controlled library, group them in pairs and perform compatibility testing on the software packages' ABI and KABI. After the testing is complete, all result data is saved and updated to the software source metadata of the controlled library. For the software packages of the specified time branch in the software source controlled library, call the interface to obtain the version-related CVE number and errata information number, generate the corresponding version vulnerability and errata information file updateinfo.xml, and update it to the software source metadata of the controlled library. The CVE number is a unique identifier for a known information security vulnerability or exposure. If the test fails, terminate and exit; otherwise, jump to step S4.

5. S4.5, perform test operations on the software source controlled library in an automated or manual manner; S4.6, if the test operation is passed, the software source executed in the specified time branch is published as the corresponding software source product library, and a product library consisting of multiple software source product libraries is obtained.

2. The software source management method capable of docking multiple compilation platforms according to claim 1, characterized in that: When the configuration selection of the software source warehouse is completed in step S1, the target compilation platform includes the KOJI compilation platform or the OBS compilation platform, and the configuration selection of the software source warehouse includes the IP address of the compilation platform, the KOJI label of the KOJI compilation platform, the OBS project of the OBS compilation platform, and part or all of the architecture.

3. The software source management method capable of docking multiple compilation platforms according to claim 1, characterized in that: The component definition file of the specified architecture or general architecture in step S1 is saved in the software source warehouse, and if an update of the component definition file is detected, the component definition file in the software source warehouse is automatically updated. The component definition file defines the software package grouping configuration, system installation form configuration and modification history of the software package in the software source warehouse, wherein the software package grouping configuration is used to support users to install a group of software packages at one time through the group installation command, the system installation form configuration is used to define the display form of the minimal installation and graphical installation of the software package, and the modification history is used to record the modification history of the software package.

4. The software source management method capable of docking multiple compilation platforms according to claim 1, characterized in that: In step S2, when the corresponding software package is updated from the target compilation platform into the software source warehouse, the corresponding software package is updated from the target compilation platform into the software source warehouse by using a source package list update or a list screening update method.

5. The software source management method capable of docking multiple compilation platforms according to claim 1, characterized in that: When generating the corresponding software source development library according to the software package source, the configuration of the software source warehouse and the component definition file in step S1, it includes generating multiple interrelated software source development libraries according to the software package source, the configuration of the software source warehouse and the component definition file. The multiple software source development libraries are used as the main source and extension source of the software package respectively, and the extension source will be generated in the controlled library together with the main source when the software source controlled library is subsequently generated; and when the software source development library is updated, the software source controlled library is generated in the controlled library according to the default latest time branch or the specified time branch in the main source and the extension source.

6. The software source management method capable of docking multiple compilation platforms according to claim 5, characterized in that: After the specified time branch is executed and the software source is published as the corresponding software source product library in step S4, it also includes locking the corresponding time branch of the software source development library in the development library and the corresponding time branch of the software source controlled library in the controlled library at the specified time branch, and using the scheduled synchronization task to synchronize the software source of the product library to the external network source to provide software source services to external network users.

7. A software source management system capable of interfacing with multiple compilation platforms, comprising a microprocessor and a memory connected to each other, characterized in that: The microprocessor is programmed or configured to execute the software source management method capable of docking with multiple compilation platforms as described in any one of claims 1 to 6.

8. A computer-readable storage medium having a computer program or instruction stored therein, characterized in that: The computer program or instruction is programmed or configured to execute, through a processor, the software source management method capable of docking with multiple compilation platforms as recited in any one of claims 1 to 6.

9. A computer program product comprising a computer program or instructions, characterized in that The computer program or instruction is programmed or configured to execute, through a processor, the software source management method capable of docking with multiple compilation platforms as recited in any one of claims 1 to 6.

Images