Methods for modifying configuration files, systems, devices, and storage media in migration scenarios.

Abstract

This invention provides a method, system, device, and storage medium for modifying configuration files in a migration scenario, belonging to the field of data processing technology. The method includes: determining reference files for difference comparison from a pre-built configuration reference file library based on the configuration file of the software to be migrated; simultaneously displaying the configuration file and reference files on a display page and performing format unification processing; highlighting the differences between the files; receiving user input for modifications to the configuration file based on the differences; and obtaining a standardized configuration file that can successfully migrate the software based on the modification input. This invention pre-centralizes the standardized configuration files of multiple successfully migrated software in a configuration reference file library, eliminating the need to access individual online software repositories to quickly obtain reference files for the configuration files of the software to be migrated. Furthermore, by directly obtaining the configuration reference files from the configuration reference file library, it saves the time spent extracting configuration files after downloading software packages online, improving the speed and efficiency of batch software migration.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, system, device, and storage medium for modifying configuration files in a migration scenario. Background Technology

[0002] Software migration involves moving a software application and its related resources from one environment to another. This often involves changes to configuration files and related dependencies and settings, which requires a reference file that allows modification of the configuration files.

[0003] Currently, modifying configuration files in migration scenarios often requires first opening web pages of different repositories or build platforms, then entering the software name to be migrated, roughly locating several successfully migrated software programs from the numerous search results, then clicking on each successfully migrated software program and downloading the software package, then extracting the corresponding reference configuration file from the software package, and finally modifying the configuration file of the software to be migrated according to the reference file.

[0004] However, because the software configuration files are scattered across various repository platforms, it is difficult for engineers to quickly and accurately locate the software that can be referenced from numerous platforms. Furthermore, the software that is found through the search still needs to be downloaded and extracted. Even if the downloaded configuration files are valuable for reference, engineers still need to manually compare them to determine which code needs to be modified, making the entire process extremely inefficient. Summary of the Invention

[0005] This invention provides a method, system, device, and storage medium for modifying configuration files in migration scenarios, which solves the problem of low efficiency in determining reference files in the prior art, and achieves efficient and rapid determination of reference files, thereby improving the efficiency of modifying configuration files in migration scenarios.

[0006] This invention provides a method for modifying configuration files in a migration scenario, comprising:

[0007] Based on the configuration file of the software to be migrated, a reference file is determined for comparison with the configuration file; the reference file is extracted from a pre-built configuration reference file library; the configuration reference file library includes specification configuration files of multiple successfully migrated software.

[0008] The configuration file and the reference file are displayed simultaneously on the display page, and the format of the display page is standardized.

[0009] Highlight the differences between the configuration file and the reference file;

[0010] Receive user input regarding modifications to the configuration file based on the differences.

[0011] Based on the modified input, the configuration file is modified to obtain a standard configuration file that can successfully migrate the software to be migrated.

[0012] According to a method for modifying configuration files in a migration scenario provided by the present invention, the step of performing format unification processing on the display page includes:

[0013] Determine several first keywords that match the configuration file and the reference file;

[0014] For each first keyword, if the first line of code containing the first keyword defines two or more parallel values, then a new second line of code is displayed on the display page to replace the first line of code.

[0015] The number of lines in the second code line is equal to the number of parallel values. The keywords of the second code line are all the first keywords, and the keyword value of the second code line is one of the two or more parallel values.

[0016] According to a method for modifying configuration files in a migration scenario provided by the present invention, the step of performing format unification processing on the display page includes:

[0017] Determine the second keyword that matches the configuration file and the reference file;

[0018] If there are patch file names with the same name in the third line of code containing the second keyword, but the order of the patch file names is different, then based on the third line of code in the configuration file, the third line of code in the reference file is modified on the display page so that the third line of code in the configuration file and the reference file are the same.

[0019] According to a method for modifying configuration files in a migration scenario provided by the present invention, the step of performing format unification processing on the display page includes:

[0020] Determine the starting keyword that matches the configuration file and the reference file;

[0021] Starting from the fourth line of code where the initial keyword is located, scan line by line until the fifth line of code is reached where the keyword does not belong to the file's code block keyword list;

[0022] Based on the fourth and fifth lines of code, the file code blocks of the configuration file and the reference file are determined;

[0023] Determine whether the keyword order of the file code blocks in the configuration file is consistent with the keyword order of the file code blocks in the reference file;

[0024] If there is a discrepancy, the order of the lines containing the keywords of the file code blocks in the reference file will be adjusted on the display page based on the keyword order of the file code blocks in the configuration file, so that the keyword order of the file code blocks in the configuration file is consistent with the keyword order of the file code blocks in the reference file.

[0025] According to a method for modifying configuration files in a migration scenario provided by the present invention, the step of performing format unification processing on the display page includes:

[0026] The configuration file is scanned line by line. If the first empty line of code is found, the scan continues line by line until the first non-empty line of code is found.

[0027] Match the second non-empty line of code in the reference file that has the same value as the first non-empty line of code, and determine the second empty line of code between the second non-empty line of code and the previous non-empty line of code.

[0028] If the first line number of the first empty code line is not equal to the second line number of the second empty code line, then the second non-empty code line is adjusted on the display page according to the first line number so that the second line number is equal to the first line number.

[0029] According to a method for modifying a configuration file in a migration scenario provided by the present invention, the step of determining a reference file for difference comparison with the configuration file of the software to be migrated includes:

[0030] Receive the software name and software version number of the configuration file input by the user;

[0031] Based on the software name and software version number of the configuration file, several candidate reference files are determined from the configuration reference file library;

[0032] The candidate reference documents are displayed on the display page in descending order of relevance scores;

[0033] Receive and respond to the user's file selection input, and determine the candidate reference file selected by the user as the reference file.

[0034] According to a method for modifying configuration files in a migration scenario provided by the present invention, the file name of the standard configuration file of the successfully migrated software includes the software name and software version number of the successfully migrated software.

[0035] This invention also provides a configuration file modification system for migration scenarios, comprising:

[0036] The data layer includes a configuration reference file library, middleware, and a search engine; the configuration reference file library and the search engine are connected through the middleware.

[0037] The service layer includes a reference file determination module, a format unification processing module, and a configuration file modification module;

[0038] The operation layer includes a difference highlighting module and a user input receiving module;

[0039] The reference file determination module is used to determine a reference file for comparison with the configuration file of the software to be migrated.

[0040] The format unification processing module is used to display the configuration file and the reference file simultaneously on the display page, and to perform format unification processing on the display page;

[0041] The difference highlighting module is used to highlight the differences between the configuration file and the reference file;

[0042] The user input receiving module is used to receive user input on modifications made to the configuration file based on the differences.

[0043] The configuration file receiving module modifies the configuration file based on the modification input to obtain a standardized configuration file that can successfully migrate the software to be migrated.

[0044] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the configuration file modification method for any of the migration scenarios described above.

[0045] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a configuration file modification method for any of the migration scenarios described above.

[0046] The present invention provides a method, system, device, and storage medium for modifying configuration files in migration scenarios. By pre-centralizing the standard configuration files of multiple successfully migrated software in a configuration reference file library, reference files for the configuration files of the software to be migrated can be quickly obtained without accessing individual online software repositories. Furthermore, by directly obtaining configuration reference files from the configuration reference file library, the time spent extracting configuration files after downloading software packages online can be saved, thereby improving the speed and efficiency of batch software migration. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0048] Figure 1 This is a flowchart illustrating the configuration file modification method for migration scenarios provided by the present invention.

[0049] Figure 2 This is a schematic diagram of the configuration file modification system for migration scenarios provided by the present invention.

[0050] Figure 3 This is a structural example diagram of the data layer provided by the present invention.

[0051] Figure 4 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0053] It should be noted that, in the description of this invention, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Those skilled in the art will understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0054] The terms "first," "second," etc., used in this invention are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more.

[0055] The following is combined Figures 1-4This invention describes the configuration file modification method, system, device, and storage medium for migration scenarios provided by the present invention.

[0056] It should be noted that all actions involving the acquisition of signals, information, or data in this invention are carried out in compliance with the relevant data protection laws and policies of the country where the invention is located, and with authorization from the owner of the relevant device.

[0057] An effective strategy for improving the ecosystem of instruction set architectures is to migrate software that is already stable on other instruction set architectures and operating systems to the instruction set architecture for which the ecosystem needs improvement; this is known as software migration. Software migration involves moving software applications and their related resources from one environment to another, which can occur between different computing platforms, architectures, operating systems, hardware environments, or cloud environments. Taking the RISC-V instruction set architecture as an example, by migrating software that is already stable on other instruction set architectures and operating systems to the RISC-V architecture, the basic software ecosystem of the RISC-V architecture can be quickly built and improved.

[0058] Software migration often involves changes to configuration files and related dependencies and settings. Modifying the configuration files of the software to be migrated by referring to those of software that has already been adapted to the instruction set architecture and successfully migrated can improve the efficiency and accuracy of the migration process.

[0059] However, there is a lack of effective reference methods in the technology of modifying the configuration files of the software to be migrated, which can be mainly divided into three aspects.

[0060] First, configuration files for successfully migrated software are often scattered across various software repositories or build platforms, making it difficult to quickly find configuration files for reference.

[0061] For example, software packages from different versions and distribution systems may migrate to the RISC-V architecture, and the contents of configuration files in different software packages may change significantly, making it difficult for engineers to accurately locate a reference version from the numerous operating system build platforms.

[0062] Secondly, finding successful migration software for reference from various software repositories or build platforms often requires a lot of screening work.

[0063] For example, for most software repositories or build platforms, entering the name of the software to be migrated will yield search results for all versions and distributions. Therefore, further filtering within these results is necessary to locate suitable software. Consequently, when multiple software migrations are required, this searching and filtering process must be repeated multiple times, making finding reference materials a highly repetitive and difficult task.

[0064] Finally, the source code and configuration files of successfully migrated software are usually included in the complete source code package of the successfully migrated software. Each configuration file requires multiple steps such as searching, filtering, downloading, and extracting from the platform to obtain.

[0065] For example, to obtain the configuration file of software that has been successfully migrated and adapted to the RISC-V architecture, one must first open the web pages of different repositories or build platforms, then enter the name of the software to be migrated, roughly locate several successfully migrated software programs for reference from the numerous search results, then click on each successfully migrated software program one by one to download the package, extract the corresponding reference configuration file from the package, and then modify the configuration file of the software to be migrated according to the reference file. On the one hand, since the source code of the successfully migrated software is stored in the build platform or repository, the specific code of the file cannot be previewed during the process of obtaining the configuration file; it must be downloaded and extracted to determine whether it has reference value, whether patch files have been added, etc. On the other hand, even if the configuration file obtained from the search and download is of reference value, engineers still need to manually compare it to determine which code needs to be modified, making the entire process extremely inefficient.

[0066] In view of this, the present invention provides a method, system, device and storage medium for modifying configuration files in migration scenarios to solve at least one of the aforementioned technical problems.

[0067] Figure 1 This is a flowchart illustrating the configuration file modification method for migration scenarios provided by the present invention, as shown below. Figure 1 As shown, the method for modifying the configuration file in the migration scenario includes, but is not limited to, the following steps 101 to 105.

[0068] It should be noted that the execution subject of the configuration file modification method for migration scenarios provided by the present invention is the configuration file modification system for the corresponding migration scenario. The modification system can be a server, computer device, such as a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.

[0069] Step 101: Based on the configuration file of the software to be migrated, determine a reference file for comparison with the configuration file.

[0070] The reference files are extracted from a pre-built configuration reference file library; the configuration reference file library includes multiple specification configuration files of successfully migrated software; the specification configuration files are configuration files that enable the software to migrate successfully during the migration process.

[0071] Specifically, multiple software packages that have been successfully migrated are obtained in advance from various repositories or build platforms. Then, specification configuration files are extracted from the software packages, and a configuration reference file library is built using these specification configuration files of successfully migrated software.

[0072] When actually migrating software, the first step is to determine the standard configuration file that will be compared with the configuration file of the software to be migrated from a pre-built configuration reference file library, based on the software name, configuration file name, software version number, or code snippets of the configuration file of the software to be migrated. This standard configuration file is then used as a reference file.

[0073] Take, for example, the software to be migrated to the RISC-V architecture in RPM (Red Hat Package Manager) format.

[0074] RPM, as a popular software format, is also a common package management tool in Linux systems. It is used by many Linux distributions such as CentOS, Fedora, and openEuler under different instruction set architectures.

[0075] When migrating software in RPM format, the software to be migrated is an RPM package with the .rpm extension. An RPM package corresponds to an RPM source package (SRPM). An RPM source package can be compiled to generate an RPM package. One RPM source package can be compiled into one or more RPM packages.

[0076] The RPM Spec file, as the configuration file for the software to be migrated, is a core component of the RPM software management system. It is also the file with the .spec extension in the RPM source code package. Generally, there is only one Spec file in an RPM source code package. The Spec file is a description file for creating the RPM package, containing a lot of information about the RPM package, such as the RPM package name, version, category, description summary, what commands to execute during creation, what operations to perform during installation, and the list of files to be included in the RPM package, etc.

[0077] Migrating an RPM package requires modifying the RPM source code package. Only through the RPM Spec can the RPM source code package be built into an RPM package. Therefore, an important step in migrating an RPM package to a RISC-V architecture is to modify the RPM Spec file of the RPM package to accommodate the changes made during the migration.

[0078] When a user wants to migrate an RPM package to a RISC-V architecture, they can enter any of the following in the search box provided by the configuration file modification system in the migration scenario: the software name of the RPM package to be migrated, the file name of the configuration file (i.e., the RPM Spec file), the software version number, or a code snippet of the configuration file. After clicking the search option, the system's search engine will match the standard configuration file of the successfully migrated software in the configuration reference file library as a reference file.

[0079] For example, users can upload a complete configuration file RPM Spec file to the configuration file upload system area provided by the configuration file modification system in the migration scenario. Then, the modification system's search engine analyzes the complete configuration file to obtain a list of matching files, so as to determine the most relevant specification configuration file of the successfully migrated software in the configuration reference file library as a reference file.

[0080] The matching file list page lists all the operating systems or build platforms involved in the matching results on the left side of the page, allowing users to easily filter the corresponding operating system or build platform through the list on the left side of the page.

[0081] The right side of the matched file list page displays multiple matching results. Each result shows the RPM package name, version number, data source, and dependency information. Clicking on any matching result on the right will take you to a detailed information display page, which shows the configuration file code and included patch file code for that RPM package. Users can upload files to be modified on this page.

[0082] It is understandable that reference files are standard configuration files that have a certain relevance or similarity to the configuration files of the software to be migrated. Standard configuration files that are not relevant or whose relevance is below a reasonable threshold are not of reference value for modifying the configuration files of the software to be migrated.

[0083] It is understandable that the configuration reference file library can consist of different successfully migrated software in at least one software migration scenario, such as different computing platforms, architectures, operating systems, hardware environments, or cloud environments, and is not limited to a specific fixed migration scenario.

[0084] Step 102: Display the configuration file and the reference file simultaneously on the display page, and perform format unification processing on the display page.

[0085] Specifically, after identifying a reference file for comparison with the configuration file of the software to be migrated, the user uploads the configuration file to be migrated. The configuration file modification system for the migration scenario then uses a file comparison tool to display both the reference file and the configuration file on the display page. For the reference file and configuration file displayed on the display page, the modification system automatically performs format standardization processing to show the standardized configuration file and reference file.

[0086] For example, the display page is mainly divided into three parts: the top is the toolbar, which provides file comparison function options; below the toolbar are two columns, the left column displays the detailed code of the reference file, and the right column displays the detailed code of the configuration file of the software to be migrated.

[0087] Step 103: Highlight the differences between the configuration file and the reference file.

[0088] Specifically, for the configuration file and reference file displayed on the display page, the file comparison tool built into the configuration file modification system in the migration scenario will automatically display the differences between the configuration file and the reference file, and highlight the differences between the two to prompt the user to modify the configuration file according to the highlighted differences.

[0089] Optionally, differences between the configuration file and the reference file can be highlighted using code differences (such as different colors). For example, red code could be used to show the unmodified code in the reference file, and green code could be used to show the modified code.

[0090] Step 104: Receive the user's input of modifications to the configuration file based on the differences.

[0091] Specifically, the display page highlights the differences between the configuration file and the reference file. The user modifies the configuration file based on the highlighted differences, and the configuration file modification system in the migration scenario receives the user's modification input.

[0092] Optionally, the modification attribute of the area displaying the configuration file on the display page is set to be modifiable, allowing users to directly modify the configuration file in real time on the display page; the modification attribute of the area displaying the reference file on the display page is set to be non-modifiable, to prevent users from accidentally modifying the reference file.

[0093] Step 105: Modify the configuration file based on the modified input to obtain a standard configuration file that can successfully migrate the software to be migrated.

[0094] Specifically, after receiving the user's modification input to the configuration file based on the differences, the user's modifications are directly retained on the configuration file based on the modification input, or the configuration file is copied to obtain a copy of the configuration file, and the user's modifications are retained on the copy of the configuration file, so as to obtain a standard configuration file that can successfully migrate the software to be migrated.

[0095] The configuration file modification method for migration scenarios provided by this invention pre-centralizes the standard configuration files of multiple successfully migrated software in a configuration reference file library. This allows for the rapid acquisition of reference files for the configuration files of the software to be migrated without accessing individual online software repositories. Furthermore, by directly obtaining the configuration reference files from the configuration reference file library, the time spent extracting configuration files after downloading software packages online can be saved, thereby improving the speed and efficiency of batch software migration.

[0096] Furthermore, this invention automatically compares configuration files and reference files using a file comparison tool, highlighting the differences between them to help users modify the configuration files of the software to be migrated based on these highlighted differences. Moreover, since configuration files for different software often have format differences due to variations in developers' coding styles, the file comparison tool also performs format standardization processing on the display page when showing configuration files and reference files. This prevents identical code content from being incorrectly displayed as differences due to different formats, reducing the time users spend identifying incorrectly displayed differences and thus improving the speed and efficiency of configuration file modification.

[0097] In one embodiment, taking the migration of RPM software to a RISC-V architecture as an example, the configuration reference file library is established based on the following steps:

[0098] The configuration reference library is determined based on RPM Spec files successfully built on the RISC-V architecture from six different repositories or platforms across three Linux distributions.

[0099] The three Linux distributions include Fedora, openSUSE, and openEuler. Fedora's specification configuration files are obtained from the Fedora official repository, the iscas-openkoji build platform, and the fedora-koji build platform. openSUSE's specification configuration files are obtained from the OBS (Open Build System) build platform, and openEuler's specification configuration files are obtained from Gitee.

[0100] For the iscas-openkoji and fedora-koji build platforms, since the successfully migrated software on these two platforms is stored in the form of SRPM, when obtaining the specification configuration file from the iscas-openkoji and fedora-koji build platforms, first filter out all SRPM packages built on RISC-V, then download the packages with "State: complete" in the Builds page of the build platform to the local machine, and then decompress and extract the RPM Spec file using the RPM tool.

[0101] Unlike the iscas-openkoji and fedora-koji build platforms, the openEuler platform stores package files directly on the Gitee open-source code hosting platform. Therefore, the RPM specification file and related files can be obtained directly using the file list link of each RPM package's master branch on the Gitee platform. Specifically, this involves scanning the repository page, obtaining the RPM package list, and downloading them one by one using `git clone`. Since a small amount of data stored on the Gitee platform is not RPM packages, the non-RPM package data is deleted after downloading.

[0102] For the Fedora platform, src-fedora data is stored in the official Fedora Git repository. Similar to the openEuler data retrieval method, you can directly use the file list link of the master branch to obtain the RPM Spec file and its related files. That is, scan the repository page, get the RPM package list, and use git clone to download them one by one.

[0103] For OpenSUSE data, it is obtained from the RISC-V build repository in the OBS build platform. Specifically, the entire repository can be cloned using the osc command-line tool.

[0104] Table 1 shows the number of specification configuration files from various sources in the configuration reference file library provided by this invention. As shown in Table 1, the Git repository is the Git repository corresponding to the built SRPM package. The SRPM package is a software package successfully built on RISC-V. The Spec is the Spec file extracted from the successfully built SRPM package. The Patch is the Patch file extracted from the successfully built SRPM package. The build information is the key information of the successfully built SRPM package and the detailed information of the build system.

[0105] Table 1

[0106]

[0107] The closer the number of standard configuration files in the configuration reference file library is to the number of configuration files stored in the software repository in real time, that is, the higher the coverage, the more specific migration scenarios the configuration file modification method for migration scenarios provided by this invention can cover, and the higher its applicability.

[0108] Furthermore, the data update function of the configuration reference file library is triggered periodically according to a preset frequency (e.g., once a day). The specific steps include:

[0109] Data monitoring involves monitoring newly generated successfully migrated software data in the software repository. A list is maintained locally, containing the hash values ​​of the commits corresponding to the names of the successfully migrated software. Each data entry is named in the format of "SRPM package name + version value + release value". The hash value is used daily to check for new data and determine whether to start the data acquisition program.

[0110] Data extraction: Extract the RPM Spec file and Patch file from the SRPM package;

[0111] Data cleaning: remove redundant files from the SRPM package extraction process, and delete the SRPM package itself.

[0112] Data storage involves storing the acquired data in a locally maintained list and configuration reference file library.

[0113] Based on the above embodiments, as an optional embodiment, the step of performing the format unification processing of the displayed page includes:

[0114] Determine several first keywords that match the configuration file and the reference file;

[0115] For each first keyword, if the first line of code containing the first keyword defines two or more parallel values, then a new second line of code is displayed on the display page to replace the first line of code.

[0116] The number of lines in the second code line is equal to the number of parallel values. The keywords of the second code line are all the first keywords, and the keyword value of the second code line is one of the two or more parallel values.

[0117] The first keyword is a keyword that appears in the configuration file and reference files and matches a keyword in the first keyword list. When the first keyword appears in the configuration file and reference files, it means that the code line containing the first keyword in the display page needs to be split and its value retrieved in a unified format.

[0118] Understandably, based on the characteristics of different keywords in the configuration file, a list of first keywords consisting of multiple first keywords can be predetermined.

[0119] Specifically, when using the file comparison tool to perform format unification processing on the display page for configuration files and reference files, regular expression matching is used on the configuration files and reference files, and the matching keyword is the first keyword in the first keyword list.

[0120] When the configuration file and reference file match several first keywords, for each first keyword, it is determined whether parallel values ​​are defined. If the first line of code containing the first keyword defines more than two parallel values, the parallel values ​​are split, and a new second line of code is displayed on the display page to replace the first line of code.

[0121] In this system, the keywords of the second code line and the first code line are both the matched first keyword. The number of lines is the number of parallel values ​​defined by the first keyword in the first code line, and the keyword value of each second code line is one of the parallel values ​​in the first code line.

[0122] Understandably, the first line of code is the line of code on the display page that has not undergone the format uniform processing of splitting and taking values ​​in parallel, and the second line of code is the line of code on the display page that has undergone the format uniform processing of splitting and taking values ​​in parallel. The first line of code has 1 or more lines, and the second line of code has 2 or more lines. The specific number of lines is determined according to the number of parallel values ​​of the first keyword.

[0123] Taking RPM Spec files as an example, different Linux distributions may have different formats due to developers' coding styles. When using the diff function to compare files, the same code content may be incorrectly displayed due to different formats. For example, line (1) in the configuration file and lines (2) and (3) in the reference file may have the same meaning, but the diff result will incorrectly display the two lines as different code, thus showing them as different content. This requires users to spend extra time identifying the lines of code that are incorrectly displayed as different content.

[0124] BuildRequires: make gcc; (1)

[0125] BuildRequires: make; (2)

[0126] BuildRequires: gcc; (3)

[0127] Therefore, it is necessary to unify the code format of RPM Spec files. That is, on the display page, the code line (1) containing the first keyword BuildRequires in the configuration file is split and its value is taken in a unified manner, and it is split into code lines (2) and (3) as shown in the reference file, so that the code line containing the keyword BuildRequires in the configuration file and the reference file will not be highlighted as different content.

[0128] Optionally, the BuildRequires first keyword is located in the first keyword list, and the complete first keyword list includes 10 first keywords: [BuildRequires, Conflicts, Provides, Requires, License, ExclusiveOS, ExcludeOS, ExclusiveArch, ExcludeArch, Conflicts].

[0129] The configuration file modification method for migration scenarios provided by this invention splits the code lines in the configuration file and reference file that match the first keyword and have parallel values ​​defined on the display page. This avoids highlighting code lines in the configuration file and reference file that have the same keyword and the same value but have parallel value definitions as differences, thus avoiding interference when users modify the code and reducing the time users spend identifying erroneous differences, thereby improving the speed and efficiency of configuration file modification.

[0130] Based on the above embodiments, as an optional embodiment, the step of performing the format unification processing of the displayed page includes:

[0131] Determine the second keyword that matches the configuration file and the reference file;

[0132] If there are patch file names with the same name in the third line of code containing the second keyword, but the order of the patch file names is different, then based on the third line of code in the configuration file, the third line of code in the reference file is modified on the display page so that the third line of code in the configuration file and the reference file are the same.

[0133] A patch file, also known as a patch file, is a text file that records the differences between two files or directories. Taking RPM Spec files as configuration files, various Linux distributions typically use patch files to modify the source code, while the RPM Spec file controls the application of the patch files. During software migration, adapting the code in the RPM Spec file that controls the application of patch files is crucial to ensuring a successful migration.

[0134] The second keyword is the patch file keyword appearing in configuration files and reference files. When the second keyword appears in configuration files and reference files, it means that the code lines in the reference files containing the second keyword, where there are patch file names with the same name but different order, need to be formatted on the display page to adjust the order of the patch file names.

[0135] The third line of code is the line of code in the configuration file and reference file whose value is defined by the second keyword.

[0136] Specifically, the configuration file and reference file are scanned line by line, with regular expressions matching the second keyword. If the third line of code containing the second keyword in the configuration file and reference file contains patch file names that are the same but in different orders, the order of the patch file names in the third line of code in the reference file is modified on the display page according to the order of the patch file names in the third line of code in the configuration file, so that the third lines of code in the configuration file and reference file are the same and are not highlighted as differences on the display page.

[0137] The configuration file modification method for migration scenarios provided by this invention matches patch file keywords that appear in both the configuration file and the reference file. When patch file names are the same but in different orders in the code line containing the patch file keyword, the order of the patch file names in the corresponding code line in the reference file is adjusted on the display page. This ensures that the code lines containing patch file keywords in the configuration file and the reference file are consistent, preventing them from being highlighted as differences. This avoids interference when users modify the code, reduces the time users spend identifying erroneously displayed differences, and thus improves the speed and efficiency of configuration file modification.

[0138] Based on the above embodiments, as an optional embodiment, the step of performing the format unification processing of the displayed page includes:

[0139] Determine the starting keyword that matches the configuration file and the reference file;

[0140] Starting from the fourth line of code where the initial keyword is located, scan line by line until the fifth line of code is reached where the keyword does not belong to the file's code block keyword list;

[0141] Based on the fourth and fifth lines of code, the file code blocks of the configuration file and the reference file are determined;

[0142] Determine whether the keyword order of the file code blocks in the configuration file is consistent with the keyword order of the file code blocks in the reference file;

[0143] If there is a discrepancy, the order of the lines containing the keywords of the file code blocks in the reference file will be adjusted on the display page based on the keyword order of the file code blocks in the configuration file, so that the keyword order of the file code blocks in the configuration file is consistent with the keyword order of the file code blocks in the reference file.

[0144] The start keyword is the first keyword in a pre-determined block of code in a file.

[0145] The file code block keyword list is a pre-determined list of keywords for each line of code within the file code block.

[0146] Optionally, if the starting keyword is %files, then %files is the starting position of the file code block.

[0147] Optionally, the list of file code block keywords includes, but is not limited to, 10 keywords: [prep, package, build, post, preun, postun, config, clean, changelog, files].

[0148] Specifically, the user file and reference file are scanned line by line, with regular expressions used to match the starting keyword. After a starting keyword is matched, the scan continues line by line from the line containing the starting keyword (line 4) until a line is found where the keyword does not belong to the file code block keyword list (line 5). The line preceding the fifth line is then identified as the end of the file code block, thus determining the file code blocks for the configuration file and reference files.

[0149] Further determine whether the keyword order of the file code blocks in the configuration file is consistent with the keyword order of the file code blocks in the reference file. If they are inconsistent, adjust the order of the code lines containing the keywords in the file code blocks in the reference file on the display page according to the keyword order of the file code blocks in the configuration file, and then adjust the keyword order to make the keyword order of the file code blocks in the configuration file and the reference file consistent.

[0150] The configuration file modification method for migration scenarios provided by this invention uses the keyword order of the file code blocks in the configuration file as the standard. The code lines of the reference file code blocks are adjusted on the display page to ensure that the keyword order of the file code blocks in the configuration file and the reference file is consistent. This avoids the situation where related code is incorrectly highlighted as difference content due to the same keyword values ​​but different keyword orders in the file code blocks. This avoids interference when users modify the code, reduces the time users spend identifying incorrectly displayed differences, and thus improves the speed and efficiency of configuration file modification.

[0151] Based on the above embodiments, as an optional embodiment, the step of performing the format unification processing of the displayed page includes:

[0152] The configuration file is scanned line by line. If the first empty line of code is found, the scan continues line by line until the first non-empty line of code is found.

[0153] Match the second non-empty line of code in the reference file that has the same value as the first non-empty line of code, and determine the second empty line of code between the second non-empty line of code and the previous non-empty line of code.

[0154] If the first line number of the first empty code line is not equal to the second line number of the second empty code line, then the second non-empty code line is adjusted on the display page according to the first line number so that the second line number is equal to the first line number.

[0155] Specifically, the unified formatting of the displayed page also includes blank line alignment. Specifically, the configuration file is scanned line by line. If the first empty line of code is found in the configuration file, the scan continues until the first non-empty line of code is found. The value of the first non-empty line of code and the line number of the first empty line of code are recorded.

[0156] In the reference file, a second non-empty line of code with the same value as the first non-empty line of code is matched. The blank lines before the second non-empty line of code in the reference file are counted, that is, the second blank line of code between the second non-empty line of code and the previous non-empty line of code, and the second line number of the second blank line of code is determined.

[0157] Check if the number of the first line is equal to the number of the second line. If they are equal, do nothing. If they are not equal, add or delete the number of the second line of empty code on the display page according to the number of the first line of the first empty code line in the configuration file, so that the number of empty code lines in the configuration file and the reference file are the same.

[0158] The configuration file modification method for migration scenarios provided by this invention scans the empty lines of code in the configuration file and reference file line by line, and adds or deletes empty lines of code in the reference file on the display page, so that the number of empty lines of code in the configuration file and reference file is the same. This avoids the same code being incorrectly highlighted as different content due to different numbers of empty lines of code in the configuration file and reference file, and will not cause interference when users modify the code. It also reduces the time for users to identify the incorrectly displayed differences, thereby improving the speed and efficiency of configuration file modification.

[0159] Understandably, when performing the format unification processing of the display page, it can be performed individually or in combination with at least one of the format unification processing methods mentioned in the above embodiments, such as splitting and listing values, adjusting the order of patch file names, adjusting the order of keywords in file code blocks, and aligning blank lines.

[0160] In one embodiment, the process of unifying the format of the display page includes: first performing blank line alignment, and then performing the format processing steps of splitting and listing values, adjusting the order of patch file names, and adjusting the order of keywords in file code blocks. The specific processing order of the three format processing steps of splitting and listing values, adjusting the order of patch file names, and adjusting the order of keywords in file code blocks can be set as needed.

[0161] Based on the above embodiments, as an optional embodiment, the step of determining a reference file for difference comparison with the configuration file of the software to be migrated includes:

[0162] Receive the software name and software version number of the configuration file input by the user;

[0163] Based on the software name and software version number of the configuration file, several candidate reference files are determined from the configuration reference file library;

[0164] The candidate reference documents are displayed on the display page in descending order of relevance scores;

[0165] Receive and respond to the user's file selection input, and determine the candidate reference file selected by the user as the reference file.

[0166] The software version number consists of one or more of the following: the release system version number, the update version number, etc.

[0167] Specifically, taking an RPM Spec file as the configuration file for the software to be migrated as an example, the filename of the RPM Spec file generally includes the software name and version number of the corresponding software to be migrated. When determining the reference file, the software name and version number of the RPM Spec file are received by the user when the operation layer of the configuration file modification system in the migration scenario is used to input the search input module.

[0168] In the migration scenario, the system's data layer search engine, based on the software name and version number in the RPM Spec file, searches the configuration reference file library for several candidate reference files. Using the search engine's built-in relevance analysis function, it displays these candidate reference files on the display page in descending order of relevance score. If no relevant candidate reference file is found, a pop-up window prompts the user that the entered software name and version number were not included or were entered incorrectly.

[0169] After the user selects candidate reference files by clicking, selecting, or using other methods, the migration scenario configuration file modification system receives and responds to the user's file selection input, and determines the candidate reference file selected by the user as the RPM Spec reference file for difference comparison.

[0170] Optionally, when matching candidate reference files, either exact matching or fuzzy matching can be used.

[0171] Optionally, after receiving and responding to the user's file selection input, the system can also access the details page of the reference file, which can display the detailed code, related patch files, and other information for the reference file.

[0172] The configuration file modification method for migration scenarios provided by this invention matches several standard configuration files from a configuration reference file library as candidate reference files based on the software name and software version number of the configuration file input by the user. The candidate reference files are then displayed to the user in descending order of relevance score. When determining candidate reference files based on relevance score, the user can intuitively select a reference file with reference value without having to manually compare all relevant candidate reference files to find the most appropriate reference file. This saves time in filtering reference files and improves the speed and efficiency of software migration, especially batch software migration.

[0173] Based on the above embodiments, as an optional embodiment, the file name of the specification configuration file of the successfully migrated software includes the software name and software version number of the successfully migrated software.

[0174] Specifically, when obtaining multiple successfully migrated software packages from various repositories or build platforms, extracting specification configuration files from the packages, and using these specification configuration files of successfully migrated software to build a configuration reference file library, the file name of each specification configuration file of successfully migrated software is named after the software name and software version number of the corresponding successfully migrated software.

[0175] The configuration file modification method for migration scenarios provided by this invention takes into account that when migrating software, it is often necessary to modify the configuration file for different distribution systems and different update versions. Therefore, when building the configuration reference file library, the file name of the configuration file is set to the software name and software version number of the successfully migrated software. This can improve the speed and efficiency of matching candidate reference files with the same name and version, and speed up the efficiency of configuration file modification.

[0176] Overall, the configuration file modification method for migration scenarios provided by this invention addresses the problems of low efficiency and high error rate in configuration file modification during software migration. It pre-collects and organizes standardized configuration files, patch files, build information, and other information from successfully migrated software, and provides visualization, retrieval and difference highlighting, file comparison, online code editing, and other means to optimize the process of obtaining reference files for software migration. This shortens the migration preparation step of configuration file modification and improves the efficiency of software migration.

[0177] Figure 2 This is a schematic diagram of the configuration file modification system for migration scenarios provided by the present invention, as shown below. Figure 2 As shown, the configuration file modification system for the migration scenario includes, but is not limited to, a data layer 210, a service layer 220, and an operation layer 230.

[0178] The data layer 210 includes, but is not limited to, a configuration reference file library 211, middleware 212, and a search engine 213; the configuration reference file library 211 and the search engine 213 are connected through middleware 212.

[0179] Service layer 220 includes, but is not limited to, reference file determination module 221, format unification processing module 222, and configuration file modification module 223.

[0180] The operation layer 230 includes, but is not limited to, the difference highlighting module 231 and the user input receiving module 232.

[0181] The reference file determination module 221 is used to determine a reference file for comparison with the configuration file of the software to be migrated.

[0182] The format unification processing module 222 is used to display the configuration file and the reference file simultaneously on the display page, and to perform format unification processing on the display page;

[0183] The difference highlighting module 231 is used to highlight the differences between the configuration file and the reference file;

[0184] User input receiving module 232 is used to receive user input on modifications made to the configuration file based on the differences in content;

[0185] The configuration file receiving module 223 modifies the configuration file based on the modified input to obtain a standard configuration file that can successfully migrate the software to be migrated.

[0186] The configuration file modification system for migration scenarios mainly consists of a data layer 210, a service layer 220, and an operation layer 230. These layers work together to achieve the desired result.

[0187] Data layer 210 serves as the cornerstone of the configuration file modification system in migration scenarios, undertaking tasks such as data storage, data synchronization, and index building.

[0188] Service layer 220 is primarily implemented in the backend and plays a core role in handling the main business logic within the configuration file modification system during migration scenarios. To ensure efficient operation and stability of the system, service layer 220 can use Go as the primary language for the server, mainly responsible for implementing various functions.

[0189] The operation layer 230 serves as the interface for direct user interaction and can be implemented as a web page. The web page is built using Vue3 and various components, implementing visual operations such as data search and filtering, and also enabling online code comparison, real-time modification, and code highlighting.

[0190] Optionally, the configuration reference file library is built on a relational database management system such as MySQL, which can achieve persistent storage.

[0191] Optionally, the middleware is Canal middleware.

[0192] Optionally, the search engine is the ElasticSearch search data analysis engine, which enables fast searching.

[0193] Figure 3 This is an example diagram of the data layer structure provided by the present invention, such as... Figure 3 As shown, the MySQL-based configuration reference file library 301 and the ElasticSearch search data analysis engine 302 are connected through the Canal middleware 303. When the configuration reference file library performs CRUD operations, the Canal middleware 303 can capture the binlog generated by these operations in real time and synchronize the binlog to the ElasticSearch search data analysis engine 302, so that the MySQL-based configuration reference file library 301 and the ElasticSearch search data analysis engine 302 can achieve data synchronization through the Canal middleware 303.

[0194] Optionally, the configuration file modification system for the migration scenario also integrates a file comparison tool.

[0195] Optionally, it also includes a search input receiving module for receiving the software name and software version number of the configuration file input by the user; and for accepting the user's file selection input to determine the candidate reference file selected by the user as the reference file.

[0196] It should be noted that the configuration file modification system for migration scenarios provided by the present invention can execute the configuration file modification method for migration scenarios described in any of the above embodiments during actual operation, which will not be elaborated in this embodiment.

[0197] The configuration file modification system for migration scenarios provided by this invention pre-centralizes the standard configuration files of multiple successfully migrated software in a configuration reference file library. This allows for the rapid acquisition of reference files for the configuration files of the software to be migrated without accessing individual online software repositories. Furthermore, by directly obtaining configuration reference files from the configuration reference file library, the time spent extracting configuration files after downloading software packages online can be saved, thereby improving the speed and efficiency of batch software migration.

[0198] Figure 4 This is a schematic diagram of the structure of the electronic device provided by the present invention, such as... Figure 4 As shown, the electronic device may include: a processor 410, a communications interface 420, a memory 430, and a communication bus 440, wherein the processor 410, the communications interface 420, and the memory 430 communicate with each other through the communication bus 440. The processor 410 can call logical instructions in the memory 430 to execute the configuration file modification method for the migration scenario provided in any of the above embodiments. The configuration file modification method for the migration scenario includes, but is not limited to, the following steps: determining a reference file for comparison with the configuration file of the software to be migrated; the reference file is extracted from a pre-built configuration reference file library; the configuration reference file library includes multiple standard configuration files of successfully migrated software; displaying the configuration file and the reference file simultaneously on a display page and performing format unification processing on the display page; highlighting the differences between the configuration file and the reference file; receiving user input for modification of the configuration file based on the differences; modifying the configuration file based on the modification input to obtain a standard configuration file that can successfully migrate the software to be migrated.

[0199] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0200] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the configuration file modification method for the migration scenario provided in any of the above embodiments. The configuration file modification method for the migration scenario includes, but is not limited to, the following steps: determining a reference file for comparison with the configuration file of the software to be migrated; the reference file is extracted from a pre-built configuration reference file library; the configuration reference file library includes multiple standard configuration files of successfully migrated software; displaying the configuration file and the reference file simultaneously on a display page and performing format unification processing on the display page; highlighting the differences between the configuration file and the reference file; receiving user input for modification of the configuration file based on the differences; modifying the configuration file based on the modification input to obtain a standard configuration file that can successfully migrate the software to be migrated.

[0201] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements the configuration file modification method for migration scenarios provided in any of the above embodiments. The configuration file modification method for migration scenarios includes, but is not limited to, the following steps: determining a reference file for comparison with the configuration file of the software to be migrated; the reference file is extracted from a pre-built configuration reference file library; the configuration reference file library includes multiple standard configuration files of successfully migrated software; displaying the configuration file and the reference file simultaneously on a display page and performing format unification processing on the display page; highlighting the differences between the configuration file and the reference file; receiving user input for modification of the configuration file based on the differences; modifying the configuration file based on the modification input to obtain a standard configuration file that can successfully migrate the software to be migrated.

[0202] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0203] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0204] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for modifying configuration files in a migration scenario, characterized in that, include: Based on the configuration file of the software to be migrated, a reference file is determined for comparison with the configuration file; The reference files are extracted from a pre-built configuration reference file library, which includes specification configuration files from multiple successfully migrated software. The configuration file and the reference file are displayed simultaneously on the display page, and the format of the display page is standardized. Highlight the differences between the configuration file and the reference file; Receive user input regarding modifications to the configuration file based on the differences. Based on the modified input, the configuration file is modified to obtain a standard configuration file that can successfully migrate the software to be migrated.

2. The method for modifying configuration files in a migration scenario according to claim 1, characterized in that, The process of unifying the format of the displayed page includes: Determine several first keywords that match the configuration file and the reference file; For each first keyword, if the first line of code containing the first keyword defines two or more parallel values, then a new second line of code is displayed on the display page to replace the first line of code. The number of lines in the second code line is equal to the number of parallel values. The keywords of the second code line are all the first keywords, and the keyword value of the second code line is one of the two or more parallel values.

3. The method for modifying configuration files in a migration scenario according to claim 1, characterized in that, The process of unifying the format of the displayed page includes: Determine the second keyword that matches the configuration file and the reference file; If there are patch file names with the same name in the third line of code containing the second keyword, but the order of the patch file names is different, then based on the third line of code in the configuration file, the third line of code in the reference file is modified on the display page so that the third line of code in the configuration file and the reference file are the same.

4. The method for modifying configuration files in a migration scenario according to claim 1, characterized in that, The process of unifying the format of the displayed page includes: Determine the starting keyword that matches the configuration file and the reference file; Starting from the fourth line of code where the initial keyword is located, scan line by line until the fifth line of code is reached where the keyword does not belong to the file's code block keyword list; Based on the fourth and fifth lines of code, the file code blocks of the configuration file and the reference file are determined; Determine whether the keyword order of the file code blocks in the configuration file is consistent with the keyword order of the file code blocks in the reference file; If there is a discrepancy, the order of the lines containing the keywords of the file code blocks in the reference file will be adjusted on the display page based on the keyword order of the file code blocks in the configuration file, so that the keyword order of the file code blocks in the configuration file is consistent with the keyword order of the file code blocks in the reference file.

5. The method for modifying configuration files in a migration scenario according to claim 1, characterized in that, The process of unifying the format of the displayed page includes: The configuration file is scanned line by line. If the first empty line of code is found, the scan continues line by line until the first non-empty line of code is found. Match the second non-empty line of code in the reference file that has the same value as the first non-empty line of code, and determine the second empty line of code between the second non-empty line of code and the previous non-empty line of code. If the first line number of the first empty code line is not equal to the second line number of the second empty code line, then the second non-empty code line is adjusted on the display page according to the first line number so that the second line number is equal to the first line number.

6. The method for modifying configuration files in a migration scenario according to claim 1, characterized in that, The reference file for comparison with the configuration file of the software to be migrated includes: Receive the software name and software version number of the configuration file input by the user; Based on the software name and software version number of the configuration file, several candidate reference files are determined from the configuration reference file library; The candidate reference documents are displayed on the display page in descending order of relevance scores; Receive and respond to the user's file selection input, and determine the candidate reference file selected by the user as the reference file.

7. The method for modifying configuration files in a migration scenario according to claim 6, characterized in that, The file name of the specification configuration file for the successfully migrated software includes the software name and software version number of the successfully migrated software.

8. A configuration file modification system for migration scenarios, characterized in that, include: The data layer includes a configuration reference file library, middleware, and a search engine; The configuration reference file library is connected to the search engine through the middleware; The service layer includes a reference file determination module, a format unification processing module, and a configuration file modification module; The operation layer includes a difference highlighting module and a user input receiving module; The reference file determination module is used to determine a reference file for comparison with the configuration file of the software to be migrated. The reference files are extracted from a pre-built configuration reference file library, which includes specification configuration files from multiple successfully migrated software. The format unification processing module is used to display the configuration file and the reference file simultaneously on the display page, and to perform format unification processing on the display page; The difference highlighting module is used to highlight the differences between the configuration file and the reference file; The user input receiving module is used to receive user input on modifications made to the configuration file based on the differences. The configuration file receiving module modifies the configuration file based on the modification input to obtain a standardized configuration file that can successfully migrate the software to be migrated.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the configuration file modification method for the migration scenario as described in any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the configuration file modification method for the migration scenario as described in any one of claims 1 to 7.

Images