CN113377386A - Installation package installation method, device and equipment without decompression - Google Patents

Abstract

The embodiments of this specification disclose a method, device, and device for installing an installation package without decompression. The scheme includes: determining the installation package to be downloaded through the package manager, and the installation package contains multiple tar files; generating an index file for the tar file according to the data in the tar file; generating a virtual read-only file system according to the index file, and combining The file system encapsulates the virtual read-only file system into a readable and writable file system; the read and write dependencies related to the installation package are established through the readable and writable file system to complete the installation of the installation package.

Description

A method, device and device for installing an installation package without decompression

technical field

This specification relates to the field of Internet technologies, and in particular, to a method, device, and device for installing an installation package without decompression.

Background technique

The package manager (Node Package Manager, npm) is a management tool for package management and distribution of Nodejs, which can realize the sharing of code and provide the convenience of using various plug-ins, libraries and frameworks.

In the process of installing and writing the npm installation package to the system, it often includes the download of a large number of tar files, and the tar files need to be decompressed into a large number of corresponding archived files, and a Nodejs project may contain thousands of tar files, which leads to writing The process takes a long time.

Based on this, a more efficient installation package installation solution without decompression is required.

SUMMARY OF THE INVENTION

One or more embodiments of this specification provide an installation package installation method, apparatus, device, and storage medium without decompression, so as to solve the following technical problem: a more efficient installation package processing solution is required.

To solve the above technical problems, one or more embodiments of the present specification are implemented as follows:

A method for installing an installation package without decompression provided by one or more embodiments of this specification includes:

Determine the installation package to be downloaded through the package manager, where the installation package contains multiple tar files;

According to the data in the tar file, generate an index file for the tar file;

generating a virtual read-only file system according to the index file, and encapsulating the virtual read-only file system into a readable and writable file system through a joint file system;

The read-write dependency related to the installation package is established through the read-write file system, so as to complete the installation of the installation package.

An installation package installation device without decompression provided by one or more embodiments of this specification includes:

Determine the module, determine the installation package to be downloaded by the package manager, and the installation package contains multiple tar files;

An index generation module, according to the data in the tar file, generates an index file for the tar file;

The system generation module generates a virtual read-only file system according to the index file, and encapsulates the virtual read-only file system into a readable and writable file system through a joint file system;

The dependency establishment module establishes read-write dependencies related to the installation package through the readable and writable file system, so as to complete the installation of the installation package.

A device for installing an installation package without decompression provided by one or more embodiments of this specification includes:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

Determine the installation package to be downloaded through the package manager, where the installation package contains multiple tar files;

According to the data in the tar file, generate an index file for the tar file;

generating a virtual read-only file system according to the index file, and encapsulating the virtual read-only file system into a readable and writable file system through a joint file system;

The read-write dependency related to the installation package is established through the read-write file system, so as to complete the installation of the installation package.

A non-volatile computer storage medium provided by one or more embodiments of this specification stores computer-executable instructions, and the computer-executable instructions are set to:

Determine the installation package to be downloaded through the package manager, where the installation package contains multiple tar files;

According to the data in the tar file, generate an index file for the tar file;

generating a virtual read-only file system according to the index file, and encapsulating the virtual read-only file system into a readable and writable file system through a joint file system;

The read-write dependency related to the installation package is established through the read-write file system, so as to complete the installation of the installation package.

The above at least one technical solution adopted by one or more embodiments of this specification can achieve the following beneficial effects: in the process of downloading the tar file, the archived files in the tar file are not decompressed, which greatly reduces the writing time of the tar file , which improves the installation speed of the installation package. At the same time, the index file is generated according to the data in the tar file, and the virtual read-only file system is generated, so that the file system has a normal dependent installation directory, which solves the problem that the dependent installation directory of the file system itself cannot be normal due to not decompressing the tar file. The problem is displayed, so as to improve the installation speed of the installation package, and at the same time, it can realize the normal browsing of the dependent installation directory by the user. At the same time, by encapsulating the readable and writable file system, users can also perform editing operations such as deletion and modification of archived files in the tar file, which enhances the flexibility of operations and optimizes the installation method of the installation package.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the following briefly introduces the accompanying drawings required in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments described in this specification. For those of ordinary skill in the art, other drawings can also be obtained according to these drawings without creative labor.

1 is a schematic flowchart of a method for installing an installation package without decompression provided by one or more embodiments of this specification;

FIG. 2 is a detailed schematic flowchart of the method in FIG. 1 under an application scenario provided by one or more embodiments of this specification;

FIG. 3 is a schematic structural diagram of a file system provided by one or more embodiments of this specification;

4 is a schematic structural diagram of an installation package installation device without decompression provided by one or more embodiments of this specification;

FIG. 5 is a schematic structural diagram of an installation package installation device without decompression provided by one or more embodiments of the present specification.

Detailed ways

The embodiments of this specification provide a method, apparatus, device, and storage medium for installing an installation package without decompression.

In order to make those skilled in the art better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings in the embodiments of this specification. Obviously, the described The embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments of the present specification, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the scope of protection of the present application.

In one or more embodiments of this specification, it is considered that by converting the tar file into a zip file, the decompression-free installation process can be realized by the properties of the zip file itself, but this also has problems, mainly as follows: if the zip file is used to realize the decompression-free installation process Unzip the installation, in the user interface, the normal dependency installation directory can no longer be seen, and the files cannot be browsed and edited, and in the programming interface, the original way of reading and writing dependencies through the file system is not feasible, destroying the existing There is ecology. Based on this, this solution also solves this problem, so as to realize a more reasonable and reliable installation without decompression.

In one or more embodiments of this specification, in the process of downloading the tar file, the archived file in the tar file is not decompressed (the archived file is taken out), which greatly reduces the writing time of the tar file and improves the performance of the tar file. The installation speed of the installation package. At the same time, the index file is generated according to the data in the tar file, and the virtual read-only file system is generated, so that the file system has a normal dependent installation directory, which solves the problem that the dependent installation directory of the file system itself cannot be normal due to not decompressing the tar file. The problem is displayed, so as to improve the installation speed of the installation package, and at the same time, it can realize the normal browsing of the dependent installation directory by the user. At the same time, by encapsulating the readable and writable file system, users can also perform editing operations such as deletion and modification of archived files in the tar file, which enhances the flexibility of operations and optimizes the installation method of the installation package. Based on such an idea, a specific description will be given below.

FIG. 1 is a schematic flowchart of a method for installing an installation package without decompression provided by one or more embodiments of the present specification. The method can be applied to different business fields, such as instant messaging business field, official business field, and so on. The process can be performed by computing devices in the corresponding field, and certain input parameters or intermediate results in the process allow manual intervention adjustments to help improve accuracy.

The flow in Figure 1 can include the following steps:

S102: Determine an installation package to be downloaded through the package manager, where the installation package includes multiple tar files.

Integrated management of multiple data sources through the package manager can determine the installation packages to be downloaded from different data sources. The installation package contains hundreds or even more tar files. During the download of the installation package, the tar files are downloaded in a certain order and written to the file system in turn.

In Unix systems and Unix-like systems, a tar file (also called a tar package or an archive file) is obtained by packaging and archiving multiple files and directories into a total file, so as to compress the tar file later. Tar files are generally merged without further compression, and can be regarded as a collection of archived files (ie, source files). In the process of writing the tar file to the file system, the tar file needs to be decompressed to obtain multiple archived files contained therein. In addition, during the decompression process, according to the location of the archived file in the tar file, determine the write position of the archived file in the file system, and establish the read-write position of the archived file in the file system based on the original mechanism of the file system. Write dependencies, get the dependency installation directory, to realize the decompression of the archived files merged in the tar file, and to realize the installation of the installation package.

The archived files in the tar file are arranged in order and downloaded in order. A tar file includes the tar header structures (ie header files) of multiple archived files and the corresponding file contents. For example, if the tar package contains two files, the tar package first stores the tar header structure of the first file, then stores the file content, then stores the tar header structure of the second file, and then stores the file content.

The package manager for Nodejs is npm. In a Nodejs project, the installation package downloaded through npm can contain thousands of tar files, and each tar file contains multiple archived files.

S104: Generate an index file for the tar file according to the data in the tar file.

In order to reduce the writing time to the file system when multiple tar files in the installation package are decompressed one by one, optimize the installation method of the installation package, and improve the installation speed of the installation package, this solution no longer decompresses the tar files in the installation package. . However, because the archived files in the tar file are not decompressed, the file system cannot index the archived files installed in the file system through the original indexing method of the system, and the corresponding dependencies cannot be displayed normally in the user interface. installation manual.

Therefore, in the process of writing the tar file into the file system, this solution generates an index file for the tar file according to the data in the tar file (ie, the archived file), so as to index the data in the tar file through the index file. The index file is associated with the location of the archived file in the tar file, and serves as the basis for browsing, viewing, and editing the corresponding archived file, which is convenient for users to browse and query the tar file in the file system.

S106: Generate a virtual read-only file system according to the index file, and encapsulate the virtual read-only file system into a readable and writable file system through a joint file system.

In one or more embodiments of this specification, the index file may be written into a corresponding directory of the file system to form a dependent installation directory. For example, build a virtual readable file system containing the tar directory (tar dir), and write the index file into the tar directory (tar dir). In this case, the tar dir includes, for example, tars and tar toc. tar package, tar toc represents the written index file.

In the case that the file system cannot index the archived files installed in the file system through the original indexing method of the system, in order to facilitate users to browse the files in the file system through the user interface and play the role of index files, this solution is based on For the index file generated in S104, a corresponding virtual read-only file system is generated, so that the user can browse and query the data in the tar file in the file system through the virtual read-only file system in the user interface.

In addition, in order to realize the user's editing operation on the files in the file system, the virtual read-only file system is encapsulated into a readable and writable file system through the Union File System (Union File System, Union FS), so that users can , the tar file can be browsed, deleted, modified and other editing operations.

Union FS is used to jointly mount multiple directories in different locations into the same directory. In this solution, after the virtual read-only file system is mounted first, a read-write layer is mounted on the existing virtual read-only file system by using the joint mounting technology, so that the read-write layer is located in the file system. At the top level, multiple read-only layers can also be mounted jointly under the read-write layer. During the operation of the file system, if a user edits a file in the file system, the changed file content will be written to the read-write layer, and the old version of the file in the virtual read-only file system will be hidden.

S108: Establish a read-write dependency related to the installation package through the read-write file system, so as to complete the installation of the installation package.

The read and write dependencies related to the installation package are established in the file system through the readable and writable file system, so that the file system can clarify the read and write dependencies between the files in the installation package and other files in the file system, and then the installation of the installation package is completed. .

Through the method in Figure 1, in the process of downloading the tar file, the archived files in the tar file are not decompressed, which greatly reduces the writing time of the tar file and improves the installation speed of the installation package. At the same time, the index file is generated according to the data in the tar file, and the virtual read-only file system is generated, so that the file system has a normal dependent installation directory, which solves the problem that the dependent installation directory of the file system itself cannot be normal due to not decompressing the tar file. The problem is displayed, so as to improve the installation speed of the installation package, and at the same time, it can realize the normal browsing of the dependent installation directory by the user. At the same time, by encapsulating the readable and writable file system, users can also perform editing operations such as deletion and modification of archived files in the tar file, which enhances the flexibility of operations and optimizes the installation method of the installation package.

Based on the method in FIG. 1 , the present specification also provides some specific implementations and extensions of the method, which will be described below.

In one or more embodiments of this specification, if the entire tar file in the installation package is downloaded and written at one time, the process of writing the tar file into the file system will be slow, time-consuming, and easily lead to Out of memory. Therefore, by streaming reading, download the tar file in the form of a data stream, read and decompress the archived files in the tar file while downloading, and decompress the tar file obtained first according to the reading order. The file is written to the file system first, and the corresponding memory can be released after some archived files are written into the file system, which can improve the file writing speed, reduce the writing time, and occupy a small amount of content to avoid memory overflow. The problem.

During the download of the tar file, the downloaded part is streamed to determine the location of the archived file in the tar file. A corresponding index file is generated according to the location of each archived file, which is used to index the archived file, so as to facilitate subsequent browsing of the archived file.

Through streaming reading, part of the downloaded files in the tar file can be processed separately and processed while downloading, which can avoid the problem of taking too long to download the tar file as a whole, and can reduce the download of tar files. time, improve the installation speed of the installation package.

Further, the index file includes the binary offset of the archived file in the tar file. According to the binary offset of the archived file in the tar file, the location information of the archived file can be determined more efficiently, which can be used as the basis for browsing and querying the archived file.

In one or more embodiments of this specification, in order to realize the browsable operation of the archived files in the tar file without decompression, the user space file system (File system in User space, fuse) can be used, according to the index The file generates a virtual read-only file system, allowing users to browse the archived files through the virtual read-only file system.

The fuse file system is a module used in Linux systems to mount the network space to the local file system, such as SSH to the local file system. With the support of the fuse kernel module, the construction of a virtual read-only file system can be realized by implementing specific file operations according to the interface provided by the fuse file system.

Further, in order to realize the editable operation of the archived file in the tar file without decompression, the virtual read-only file system can be overwritten by the overlay file system to encapsulate the virtual read-only file system into a readable and writable file system. File system. Users can read and browse the archived files through the readable and writable file system, and edit and modify them at the same time.

The overlay file system is a new type of union file system that usually contains two file systems: the upper file system (upper dir) and the lower file system (lower dir). The upper file system is writable, and the lower file system is read-only. The file existing in the upper file system will overwrite the file with the same name in the lower, but for the directory, the file with the same name will be overwritten, and the files with different names will be merged. The lower file system can be any file system supported by the Linux system. Therefore, in this solution, the virtual read-only file system is used as the lower file system.

In this solution, the upper file system can be used for file browsing and editing, and the virtual read-only file system is only used for file browsing. In the initial situation, the files in the upper file system and the virtual read-only file system are consistent, and in the subsequent use of the file system, try to maintain the consistency of the files in the upper file system and the virtual read-only file system.

Specifically, during the use of the file system, when the user performs a file browsing operation, if there is no file in the upper file system but there is a file in the virtual read-only file system, file browsing is performed from the virtual read-only file system; If there is a file in the file system but no file exists in the virtual read-only file system, file browsing is performed from the upper file system; if there are files in both the virtual read-only file system and the upper file system, file browsing is performed from the upper file system.

When a user edits and modifies a file, if the file only exists in the upper file system, the file is edited from the upper file system; if the file exists in the virtual read-only file system and the upper file system, the file is edited from the upper file system. Edit; if the file only exists in the virtual read-only file system, through the copy_up operation, first copy the file from the virtual read-only file system to the upper file system, create a hard link for the file, and then copy the file from the upper file system. Perform file editing, that is, two new files are generated in the upper file system directory. The file editing operation only takes effect on the files in the upper file system, and the files in the virtual read-only file system remain unchanged.

When a user deletes a file, if the file exists in the virtual read-only file system and the upper file system, the file in the upper file system will be deleted, and a "without" file will be created in the upper file system directory, while the virtual file system will be deleted. The file in the read-only file system will not be deleted; if the file only exists in the virtual read-only file system, a "without" file will be created in the upper file system directory according to the file, as the file has been removed from the upper file system. is marked for deletion, while files in virtual read-only filesystems are not deleted. If you need to delete a directory that exists in both the virtual read-only file system and the upper file system, the directory in the upper file system will be deleted, and an "opaque" directory similar to the "without" file will be created in the directory of the upper file system, and Directories in virtual read-only filesystems are not deleted.

Through the above operations on the files in the file system, it can be obtained that since the virtual read-only file system is a read-only system, the editing operations on files and directories are all performed on the files or directories in the upper file system. When making changes to the overlay file system, only the files in the upper file system are modified.

Further, during or after the installation of the installation package, through the readable and writable file system or the virtual read-only file system, the current dependent installation directory corresponding to the installation package can be displayed on the user interface; Directory directives to edit tar files through a readable and writable filesystem.

In one or more embodiments of this specification, according to the read and write dependencies related to the installation package in the file system, a part of tar files with dependencies are selected from multiple tar files, and the part of tar files with dependencies are spliced together , to get the concatenated tar file. Generate an index file for the concatenated tar file and update it to a virtual read-only file system. There is an association relationship between tar files with dependencies. The spliced tar files are obtained by splicing the tar files with dependencies, and an index file corresponding to the spliced tar files is generated, which is conducive to providing convenience for users to index tar files. It is also convenient for the file system to query some tar files with dependencies.

Based on the sequential download of tar files, during the splicing process, the tar files are also spliced according to the order and position of the dependent tar files to obtain the corresponding spliced tar files, so as to realize the correct installation and Browse.

In one or more embodiments of this specification, in practical applications, some installation packages may be updated frequently, especially installation packages of a testing nature or installation packages that require more branch versions in research and development. For such installation packages, in order to It is convenient to update and improve the installation efficiency. Consider not to perform persistent installation, but to borrow the cache of the package manager to maintain a state of dynamic installation waiting to be updated at any time. Based on this, the cache allocated to the package manager can be determined, and the read-write dependencies related to the installation package can be established in the cache through the read-write file system. Of course, the virtual read-only file system and the read-write file system can directly It is built in this cache, so that subsequent update installations can be completed without the package manager, and the read and write efficiency is higher.

In combination with the foregoing description, one or more embodiments of this specification provide a detailed flowchart of the method in FIG. 1 under an application scenario, and some of the previous optional solutions are used in the process, and the process is shown in FIG. 2 . Show.

In the process of Figure 2, the installation package to be installed includes thousands of tar files. Without decompressing the archived files in the tar file, in order to realize the browsing of the archived files, according to the archived files in the tar file The file (ie, the source file) generates a corresponding index file for indexing the archived file.

According to the index file, generate the fuse file system. The fuse file system is a virtual read-only file system that can be used to browse and query the archived files in the installed tar file.

The fuse file system is encapsulated as an overlay file system, and the overlay file system is a readable and writable file system. Through the encapsulation, users can modify and delete the archived files in the installed tar file through the overlay file system. Edit operations.

During the installation process or after the installation, the read and write dependencies related to the installation package are established through the overlay file system to complete the installation process of the installation package.

Through the fuse file system or the overlay file system, the established read-write dependent directories (ie, dependent installation directories) can be displayed in the user interface, so that users can browse and view the data in the tar file installed in the file system.

Through the overlay file system, editing operations such as modification and deletion of the corresponding tar file can be performed based on the user's instructions for the dependent installation directory.

With reference to the foregoing description, one or more embodiments of this specification provide a schematic structural diagram of a file system, as shown in FIG. 3 .

In the file system shown in Figure 3, through the fuse file system, a virtual read-only file system is generated according to the index file, and the user can use the fuse file system to perform operations on the data in the tar file (that is, the archived file) installed in the system. Browse queries.

The tar directory in the file system can be used to write index files. The tar directory includes tars and tar toc. tars can be used to provide a development framework based on the tars protocol, and tar toc can be used to generate directories.

Through the overlay file system, the fuse file system is encapsulated to generate a readable and writable file system. Users can browse and edit the data in the tar file installed in the system through the overlay file system. Among them, the overlay file system includes the upper file system and the fuse file system (for example, it is used as the lower file system), and the worker directory is used for files during the operation of the overlay.

Based on the same idea, one or more embodiments of the present specification also provide apparatuses and devices corresponding to the foregoing methods, as shown in FIG. 4 and FIG. 5 .

4 is a schematic structural diagram of an installation package installation device without decompression provided by one or more embodiments of the present specification, and the device includes:

Determining module 402, determining an installation package to be downloaded by the package manager, where the installation package contains multiple tar files;

The index generation module 404 generates an index file for the tar file according to the data in the tar file;

The system generation module 406 generates a virtual read-only file system according to the index file, and encapsulates the virtual read-only file system into a readable and writable file system through a joint file system;

The dependency establishing module 408 establishes read-write dependencies related to the installation package through the read-write file system, so as to complete the installation of the installation package.

Optionally, the index generation module 404, in the downloading process of the tar file, performs streaming reading on the downloaded part to determine the location of the archived file in the tar file; according to the location A corresponding index file is generated for indexing the archived file.

Optionally, the index file includes the binary offset of the archived file in the tar file.

Optionally, the system generation module 406 generates a virtual read-only file system according to the index file through the fuse file system; and encapsulates the virtual read-only file system into a readable and writable file system through the overlay file system.

Optionally, the apparatus further includes a presentation editing module 410; the presentation editing module 410 executes, during or after the installation of the installation package: through the readable and writable file system or the virtual read-only file The system displays the currently corresponding dependent installation directory of the installation package on the user interface; and, in response to the user's instruction for the dependent installation directory, edits the tar file through the readable and writable file system.

Optionally, the device further includes a splicing module 412; the splicing module 412, according to the read-write dependency, selects a part of the tar files with dependencies from the multiple tar files; The tar file is spliced to obtain a spliced tar file; an index file is generated for the spliced tar file, and updated to the virtual read-only file system.

Optionally, the dependency establishment module 408 determines the cache allocated to the package manager;

A read-write dependency related to the installation package is established in the cache through the read-write file system.

Optionally, the package manager includes an npm package manager under Nodejs.

FIG. 5 is a schematic structural diagram of an installation package installation device without decompression provided by one or more embodiments of this specification, and the device includes:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

Determine the installation package to be downloaded through the package manager, where the installation package contains multiple tar files;

According to the data in the tar file, generate an index file for the tar file;

generating a virtual read-only file system according to the index file, and encapsulating the virtual read-only file system into a readable and writable file system through a joint file system;

The read-write dependency related to the installation package is established through the read-write file system, so as to complete the installation of the installation package.

Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium corresponding to the above method, storing computer-executable instructions, and the computer-executable instructions are set to:

Determine the installation package to be downloaded through the package manager, where the installation package contains multiple tar files;

According to the data in the tar file, generate an index file for the tar file;

generating a virtual read-only file system according to the index file, and encapsulating the virtual read-only file system into a readable and writable file system through a joint file system;

The read-write dependency related to the installation package is established through the read-write file system, so as to complete the installation of the installation package.

In the 1990s, improvements in a technology could be clearly differentiated between improvements in hardware (eg, improvements to circuit structures such as diodes, transistors, switches, etc.) or improvements in software (improvements in method flow). However, with the development of technology, the improvement of many methods and processes today can be regarded as a direct improvement of the hardware circuit structure. Designers almost get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware entity modules. For example, a Programmable Logic Device (PLD) (eg, Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. It is programmed by the designer to "integrate" a digital system on a PLD without having to ask the chip manufacturer to design and manufacture a dedicated integrated circuit chip. And, instead of making integrated circuit chips by hand, these days, much of this programming is done using software called a "logic compiler", which is similar to the software compiler used in program development and writing, but before compiling The original code also has to be written in a specific programming language, which is called Hardware Description Language (HDL), and there is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (RubyHardware Description Language), etc. The most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be clear to those skilled in the art that a hardware circuit for implementing the logic method process can be easily obtained by simply programming the method process in the above-mentioned several hardware description languages and programming it into the integrated circuit.

The controller may be implemented in any suitable manner, for example, the controller may take the form of eg a microprocessor or processor and a computer readable medium storing computer readable program code (eg software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicon Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in the form of pure computer-readable program code, the controller can be implemented as logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded devices by logically programming the method steps. The same function can be realized in the form of a microcontroller, etc. Therefore, such a controller can be regarded as a hardware component, and the devices included therein for realizing various functions can also be regarded as a structure within the hardware component. Or even, the means for implementing various functions can be regarded as both a software module implementing a method and a structure within a hardware component.

The systems, devices, modules or units described in the above embodiments may be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.

For the convenience of description, when describing the above device, the functions are divided into various units and described respectively. Of course, when implementing this specification, the functions of each unit may be implemented in one or more software and/or hardware.

As will be appreciated by one skilled in the art, the embodiments of the present specification may be provided as a method, a system, or a computer program product. Accordingly, embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The specification is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-persistent memory in computer readable media, random access memory (RAM) and/or non-volatile memory in the form of, for example, read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media includes both persistent and non-permanent, removable and non-removable media, and storage of information may be implemented by any method or technology. Information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Flash Memory or other memory technology, Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device comprising a series of elements includes not only those elements, but also Other elements not expressly listed, or which are inherent to such a process, method, article of manufacture, or apparatus are also included. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article of manufacture, or device that includes the element.

This specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the apparatus, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and reference may be made to some descriptions of the method embodiments for related parts.

The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The above descriptions are merely one or more embodiments of the present specification, and are not intended to limit the present specification. Various modifications and variations of the one or more embodiments of this specification are possible for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims (17)

1. A decompression-free installation package installation method, comprising:

determining an installation package to be downloaded through a package manager, wherein the installation package comprises a plurality of tar files;

generating an index file for the tar file according to the data in the tar file;

generating a virtual read-only file system according to the index file, and packaging the virtual read-only file system into a read-write file system through a combined file system;

and establishing read-write dependence related to the installation package through the read-write file system so as to complete installation of the installation package.

2. The method according to claim 1, wherein generating an index file for the tar file according to the data in the tar file specifically includes:

in the downloading process of the tar file, performing streaming reading on a downloading part to determine the position of an archived file in the tar file;

and generating a corresponding index file according to the position for indexing the archived file.

3. The method of claim 2, the index file comprising a binary offset of the archived file in the tar file.

4. The method according to claim 1, wherein the generating a virtual read-only file system according to the index file and packaging the virtual read-only file system into a readable and writable file system by using a combined file system specifically comprises:

generating a virtual read-only file system according to the index file through a fuse file system;

and encapsulating the virtual read-only file system into a read-write file system through an overlay file system.

5. The method of claim 1, during or after installation of the installation package, further comprising:

displaying a dependent installation directory currently corresponding to the installation package on a user interface through the read-write file system or the virtual read-only file system; and the number of the first and second groups,

and editing the tar file through the readable and writable file system in response to a user instruction for the dependent installation directory.

6. The method of claim 1, further comprising:

selecting a part of tar files with dependency relationship from the plurality of tar files according to the read-write dependency;

splicing the part of tar files with the dependency relationship to obtain spliced tar files;

and generating an index file for the spliced tar file, and updating the index file to the virtual read-only file system.

7. The method according to claim 1, wherein the establishing of the read-write dependency related to the installation package by the readable-writable file system specifically comprises:

determining a cache allocated to the packet manager;

and establishing read-write dependence related to the installation package in the cache through the read-write file system.

8. The method of any of claims 1 to 7, the package manager comprising an npm package manager under Nodejs.

9. A non-decompression installation kit installation device comprising:

the determining module is used for determining an installation package to be downloaded through the package manager, and the installation package comprises a plurality of tar files;

the index generation module is used for generating an index file for the tar file according to the data in the tar file;

the system generation module generates a virtual read-only file system according to the index file and encapsulates the virtual read-only file system into a read-write file system through a combined file system;

and the dependence establishing module is used for establishing read-write dependence related to the installation package through the read-write file system so as to complete the installation of the installation package.

10. The apparatus according to claim 9, wherein the index generating module, during the downloading of the tar file, performs streaming reading on the downloaded part to determine a location of an archived file in the tar file;

and generating a corresponding index file according to the position for indexing the archived file.

11. The apparatus of claim 10, the index file comprising a binary offset of the archived file in the tar file.

12. The apparatus of claim 9, the system generation module to generate, by a fuse file system, a virtual read-only file system from the index file;

and encapsulating the virtual read-only file system into a read-write file system through an overlay file system.

13. The apparatus of claim 9, further comprising a show editing module;

the display editing module executes the following steps in the installation process or after the installation of the installation package:

displaying a dependent installation directory currently corresponding to the installation package on a user interface through the read-write file system or the virtual read-only file system; and the number of the first and second groups,

and editing the tar file through the readable and writable file system in response to a user instruction for the dependent installation directory.

14. The apparatus of claim 9, further comprising a stitching module;

the splicing module selects a part of tar files with dependency relationship from the plurality of tar files according to the read-write dependency;

splicing the part of tar files with the dependency relationship to obtain spliced tar files;

and generating an index file for the spliced tar file, and updating the index file to the virtual read-only file system.

15. The apparatus of claim 9, the dependency establishment module to determine a cache allocated to the packet manager;

and establishing read-write dependence related to the installation package in the cache through the read-write file system.

16. The apparatus of any of claims 9 to 15, the packet manager comprising an npm packet manager under nodjs.

17. An installation package installation apparatus without decompression, comprising:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

determining an installation package to be downloaded through a package manager, wherein the installation package comprises a plurality of tar files;

generating an index file for the tar file according to the data in the tar file;

generating a virtual read-only file system according to the index file, and packaging the virtual read-only file system into a read-write file system through a combined file system;

and establishing read-write dependence related to the installation package through the read-write file system so as to complete installation of the installation package.

Images