Packing method of application dependent self-contained technology under linux system

Abstract

The invention belongs to the field of computer software, and particularly relates to a packaging method for an application dependent self-contained technology under a linux system. The method comprises the following steps: creating a squashfs file; starting a systemd-mount automatic mounting service to complete the automatic creation of a mounting point; operating an entry control script, and guiding an environment variable to a file system under a directory of the mounting point by detecting a system environment; starting a Preloader module, and dynamically modifying the environment variable into a path of a dynamic linker in the file system of the mounting point in real time. The invention has the beneficial effects that there is no dependency on original library files in a system, the influence of system software package upgrading on an internal environment of a self-dependent package is completely isolated, and the environment of the system is not influenced; the system can interact with existing software packages of the system, and software such as a browser and the like of the system can be called and can also be called by software in the system; cross-release version release of running software is supported.

Description

technical field [0001] The invention belongs to the field of computer software, and in particular relates to a packaging method for application-dependent self-contained technology under a Linux system. Background technique [0002] In the distribution of the Linux operating system, each distribution will update and iterate its own system according to its own release cycle, and each iteration will release a new set of software packages. It is difficult to change the relationship across versions, especially for i386 architecture applications in the current mainstream x86_64 environment, there are often dependency problems such as missing dependent packages or version mismatches. In a self-dependent environment, its most basic and critical dependent packages Libc6:i386 is even slightly different from the original libc6:i386 in the system, which will cause program running errors. [0003] Existing methods commonly found in current linux distributions are listed below: [0004]...

AI Technical Summary

Problems solved by technology

[0007] 1. Tools such as flatpak and snap that use container technology shield the difference in system version through container technology, and install a system version similar to the release version in the container, which takes up a lot of disk space and wastes system resources

[0008] 2. The flatpak and snap application stores are in the hands of foreign distribution manufacturers. It is extremely inconvenient for domestic users to install or submit applications. It is very difficult for users to make and install their own software packages

[0009] 3. Due to the limitation of the container, there are many restrictions in application development. For example, the application in the container cannot call the system's own input method, the system's own browser, etc. Although the publisher has implemented it for many years, it is still rarely accepted by users

[0010] 4. Also due to the isolation limitation of container technology, applications inside the container cannot use the latest software resources outside the container, resulting in no reason for the release version to be updated

[0012] 1. The AppImage program decompresses the package to the / tmp directory when it is running, and deletes the temporary files generated by decompression when the program is running, which is inefficient when the software package is relatively large

[0013] 2. The AppImage program will generate a separate instance each time it runs, which will cause a large number of duplicate instances to be generated synchronously when running multiple program instances, resulting in unnecessary waste of system resources

[0014] 3. Each AppImage program exists in isolation, and cannot be called by other applications in the system, nor can it be called by other applications in the system. It is not managed by the existing program installer in the system, which may easily cause system confusion

[0015] 4. The package of i386 architecture will depend on libc:i386 in the system, and the cross-platform feature will be affected

Images