CN117331573A - Bootstrapped lightweight software package installation method - Google Patents
Bootstrapped lightweight software package installation method Download PDFInfo
- Publication number
- CN117331573A CN117331573A CN202311046161.XA CN202311046161A CN117331573A CN 117331573 A CN117331573 A CN 117331573A CN 202311046161 A CN202311046161 A CN 202311046161A CN 117331573 A CN117331573 A CN 117331573A
- Authority
- CN
- China
- Prior art keywords
- package
- software
- packages
- software package
- files
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000009434 installation Methods 0.000 title claims abstract description 28
- 238000000034 method Methods 0.000 title claims abstract description 20
- 230000006978 adaptation Effects 0.000 abstract description 4
- 230000007704 transition Effects 0.000 abstract description 4
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000011900 installation process Methods 0.000 abstract description 2
- 235000003197 Byrsonima crassifolia Nutrition 0.000 description 4
- 240000001546 Byrsonima crassifolia Species 0.000 description 4
- 235000012012 Paullinia yoco Nutrition 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Abstract
The invention relates to a bootstrapping lightweight software package installation method, which comprises the following steps: s1: extracting a plurality of software packages and/or files in a plurality of formats according to different functions or requirements; s2: according to step S1, software packages and/or files extracted according to different functions are made into big software packages with bootstrap functions, and the formats of the big software packages are the same; s3: uploading each big software package to a warehouse for managing the software packages; s4: the user downloads the software package according to the requirement and installs the software package by one key. The beneficial effects of the invention are as follows: the adaptation and the installation process of the software package are separated, the adaptation of the software package is delivered to maintainers, and the user only needs to install the software package. The installation and the management of a plurality of software packages are realized on the basis of being compatible with the original software package manager. For files that provide version transition requirements, they are no longer provided in the form of documents and software.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a bootstrapping lightweight software package installation method.
Background
During use, an operating system often encounters a feature or function that corresponds to a series of files, divided into configuration files, executable files, description files, and the like. The features or functions are typically subdivided into individual basic packets, which are most often provided in the form of deb or rpm packets (whether deb or rpm packets depend on the particular operating system). But there are scenarios where it is inconvenient to use the format of these packets to provide:
scene one: a large feature that relies on multiple deb packets (or rpm packets) needs to be supported, which is inconvenient when the user needs to install multiple packets one by one.
Scene II: it is not necessary to make the entire package again when a certain file in a certain deb package (or rpm package) of the operating system needs to be updated, especially when a transition scheme is adopted to temporarily update a certain file.
For scenario one: the method for installing a plurality of packages comprises the step of installing each package one by one according to a description document of the installation of a certain characteristic, and the installation of each package can have a dependence problem, namely, the middle process needs to be tried by one. It is not friendly for the user, who is not concerned about what packages need to be installed, but wants this feature to be available.
For scenario two: for temporary bug, only updating the file of a certain package, and adopting a transitional solution before the next version update: firstly, reproducing the whole package, giving an explanation document and informing the updated step; and secondly, giving a file for describing the document and the update, and describing the update step. It is also obviously inconvenient for the user and the temporary solution is not maintenance friendly.
At present, the Chinese patent invention (CN 101271391A) provides a method for manufacturing and using a software system, which comprises the following steps: determining a plurality of modules from code written for the software system, each module for implementing a function; determining a module required to implement a predetermined function from among a plurality of modules; and separately making an installation package for each required module. The invention reduces the installation time and the installation space and is convenient for the use of software. The patent addresses the problem of creating a piece of software from the beginning, implementing the required dependency file classification as a distinct module, essentially the creation of the original package, without the help of existing RPM or DEB packages.
The Chinese patent "method and apparatus for processing components" (patent number: CN 108255499A) provides a method and apparatus for processing components. In the method, the native RPM package is decomposed to be finally converted into the TAR package, and component version information contained in the component dependency relationship in the RPM package is deleted in the process of converting the RPM package into the TAR package, so that the coupling requirement between components is weakened, the version upgrading of a single component can be realized, and the flexibility of component version selection is provided. While this patent enables the installation of components, it is virtually undesirable for our solution to destroy the original RPM or DEB packet dependencies.
Disclosure of Invention
The main object of the present invention is to provide a solution for a user to install a certain property or to update a certain file in a package by one key, especially for the two above mentioned scenarios.
In order to accomplish the above object, the present invention provides a bootstrapped lightweight software package installation method, comprising the steps of:
s1: extracting a plurality of software packages and/or files in a plurality of formats according to different functions or requirements;
s2: according to step S1, software packages and/or files extracted according to different functions are made into big software packages with bootstrap functions, and the formats of the big software packages are the same;
s3: uploading each big software package to a warehouse for managing the software packages;
s4: the user downloads the software package according to the requirement and installs the software package by one key.
Preferably, in step S1, when all extracted according to functions or requirements are software packages, step S2 can be replaced by: the storage links of the software packages are extracted and synthesized into a large software package with bootstrap function.
Preferably, in step S2, when the software package and the file are included after being extracted according to the function or the requirement, the file is first made into a sub-software package, and the sub-software package and the remaining software package are made into a large software package with the bootstrap function.
Preferably, in step S2, when all the files extracted according to the function or the requirement are files, the files are first made into sub-packages, and the sub-packages are made into large packages with bootstrap functions.
Further preferably, the software package in step S1 includes a bin package, a deb package, and an rpm package.
Still more preferably, the large software package completed in step S2 is a bin package.
The beneficial effects of the invention are as follows:
(1) The adaptation and the installation process of the software package are separated, the adaptation of the software package is delivered to maintainers, and the user only needs to install the software package.
(2) The installation and the management of a plurality of software packages are realized on the basis of being compatible with the original software package manager.
(3) For files that provide version transition requirements, they are no longer provided in the form of documents and software.
(4) The installation forms of a plurality of software packages and files used by version transition requirements are unified, and the large software package is simple and flexible to manufacture; the user installs by one key, and the operation is succinct.
Detailed Description
The technical solutions in the embodiments of the present invention are clearly and completely described below in conjunction with the embodiments of the present invention. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, but the present invention may be practiced in other ways other than those described herein, and persons skilled in the art will readily appreciate that the present invention is not limited to the specific embodiments disclosed below.
Example 1
This embodiment is described by taking installation yopto as an example.
The installation of yoco only needs to download the code of yoco by a defunctation network, and the process of acquiring the git is carried out by executing the git clone git:// git. Yoco project. Org/poky and then executing the operation required by yoco. However, some of the column operations of yopto are matched by the related packages, i.e., yopto is in need of an installation environment as follows:
$ sudo apt-get update
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat cpio python python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping libsdl1.2-dev xterm
here the apt-get commands are installed as individual deb packets.
For the above scenario, instead of providing documents and files or packages to be upgraded, the user really expects a simple way to tell the user how to operate; on the other hand, a maintainer of an operating system also needs a simple and maintenance-friendly way to meet the demands of users.
And in order to facilitate the installation of users, the method can be realized by the following steps:
s1: extracting the deb packets according to the requirements of the installation environment;
s2: according to step S1, the extracted deb packet is manufactured into a bin packet; alternatively, the deb packet storage link is made as a bin packet so that individual deb packets are downloaded one by means of commands when the user installs the packet.
S3: uploading the bin package to a warehouse for managing the software package;
s4: the user downloads the software package according to the requirement and installs the software package by one key.
Example two
The present embodiment is still described by taking installation yopto as an example.
In this embodiment, the installation environment of yopto has a guide document, but may fail for different operating system versions, such as the dependence of the software package and the conflict problem, so the following operation steps may also be performed:
s1: extracting the deb packets and files according to the requirements of the installation environment;
s2: according to step S1, these deb packets are made into bin packets; firstly, preparing all extracted files into sub-software packages, and then preparing bin packages from the sub-software packages;
s3: uploading all bin packages to a warehouse for managing the software packages;
s4: the user downloads the software package according to the requirement and installs the software package by one key.
Example III
Sometimes the operating system needs to provide on-line solutions, such as to upgrade a file, but the file is embedded in a package, which is not necessary if the entire package is not convenient to provide. However, if this file is provided separately, it is necessary to inform the customer how to install it, and to provide the file with additional description documentation (as opposed to being a unified package previously), which is not maintenance-friendly.
For example, a module x.ko of an operating system kernel requires online updates, but the kernel module is initially released to the client by an integral kernel module package (with many modules with suffixes. Ko inside). In addition to replacing the x.ko module on-line, the associated dependent program needs to be suspended, which may require a series of operations, so a description document is needed to describe how to operate.
For the above scenario, instead of providing documents and files or packages to be upgraded, the user really expects a simple way to tell the user how to operate; on the other hand, a maintainer of an operating system also needs a simple and maintenance-friendly way to meet the demands of users.
In order to solve the above problems, the solution provided in this embodiment is as follows:
s1: extracting all files according to the above-mentioned request;
s2: according to the step S1, the extracted file is manufactured into a patch package, and then the patch package is manufactured into a bin package;
s3: uploading the bin package to a warehouse for managing the software package;
s4: the user downloads the software package according to the requirement and installs the software package by one key.
It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Claims (6)
1. A bootstrapped lightweight software package installation method, comprising the steps of:
s1: extracting a plurality of software packages and/or files in a plurality of formats according to different functions or requirements;
s2: according to step S1, software packages and/or files extracted according to different functions are made into big software packages with bootstrap functions, and the formats of the big software packages are the same;
s3: uploading each big software package to a warehouse for managing the software packages;
s4: the user downloads the software package according to the requirement and installs the software package by one key.
2. A bootstrapped lightweight software package installation method according to claim 1, wherein in step S1, when all the software packages extracted according to functions or requirements are software packages, then step S2 can be replaced by: the storage links of the software packages are extracted and synthesized into a large software package with bootstrap function.
3. The bootstrapping lightweight package installation method according to claim 1, wherein in step S2, when the software package and the file are included after being extracted according to the function or requirement, the file is first made into a sub-package, and the sub-package and the remaining software package are made into a large package with a bootstrapping function.
4. The bootstrapping lightweight package installation method according to claim 1, wherein in step S2, when all files extracted according to functions or requirements are files, the files are first made into sub-packages, and the sub-packages are made into large packages with bootstrap functions.
5. A bootstrapped lightweight package installation method according to any of claims 1-4, wherein the software package in step S1 comprises a bin package, a deb package, an rpm package.
6. The bootstrapping lightweight package installation method of claim 5, wherein the large software package fabricated in step S2 is a bin package.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311046161.XA CN117331573A (en) | 2023-08-18 | 2023-08-18 | Bootstrapped lightweight software package installation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311046161.XA CN117331573A (en) | 2023-08-18 | 2023-08-18 | Bootstrapped lightweight software package installation method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117331573A true CN117331573A (en) | 2024-01-02 |
Family
ID=89277984
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311046161.XA Pending CN117331573A (en) | 2023-08-18 | 2023-08-18 | Bootstrapped lightweight software package installation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117331573A (en) |
-
2023
- 2023-08-18 CN CN202311046161.XA patent/CN117331573A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7310801B2 (en) | Servicing a component-based software product throughout the software product lifecycle | |
| US7934210B1 (en) | System and method for updating one or more programs and their environment | |
| US5752042A (en) | Server computer for selecting program updates for a client computer based on results of recognizer program(s) furnished to the client computer | |
| KR101075388B1 (en) | Peripheral device driver maintenance scheme for networked peripheral device clients | |
| US6385623B1 (en) | System and method for ensuring proper execution of scheduled file updates | |
| US6996815B2 (en) | Method and software tools for intelligent service pack installation | |
| US6493871B1 (en) | Method and system for downloading updates for software installation | |
| US7356816B2 (en) | Method and apparatus for multiplatform migration | |
| US7062764B2 (en) | System and method for manipulating offline software | |
| US6370646B1 (en) | Method and apparatus for multiplatform migration | |
| CN102622241B (en) | A kind of method for upgrading software and device | |
| US8392906B2 (en) | Enabling parallel websphere runtime versions | |
| US6748591B1 (en) | Method, system, program, and data structures for loading programs into a runtime environment | |
| US8312446B2 (en) | Dependency management when upgrading application components | |
| EP1577766A2 (en) | Side-by-side drivers | |
| KR20020047709A (en) | System for upgrading device driver and method for upgrading the same | |
| US20110173606A1 (en) | Information processing apparatus, control method thereof, and program | |
| US20020091720A1 (en) | Methods and arrangements for providing improved software version control in managed devices | |
| CN101326515A (en) | Metadata driven deployment of applications | |
| CN117331573A (en) | Bootstrapped lightweight software package installation method | |
| US20070079279A1 (en) | Embedded device with software registry | |
| CN112328295A (en) | Software updating method and device | |
| JP2008204208A (en) | Automatic generation system of patch application procedure, automatic generation method of patch application procedure and program | |
| JP2002189601A (en) | Program installing method and program installing system | |
| CN117931261A (en) | Modularized deployment method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |