CN102654835B - (SuSE) Linux OS distribution method for making - Google Patents
(SuSE) Linux OS distribution method for making Download PDFInfo
- Publication number
- CN102654835B CN102654835B CN201210137397.XA CN201210137397A CN102654835B CN 102654835 B CN102654835 B CN 102654835B CN 201210137397 A CN201210137397 A CN 201210137397A CN 102654835 B CN102654835 B CN 102654835B
- Authority
- CN
- China
- Prior art keywords
- software package
- title
- software
- download
- downloaded
- 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.)
- Active
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of (SuSE) Linux OS distribution method for making.The method comprises: obtain the configuration information about software package, software package and their download path, determines that each software package group name claims and download path and each software package title and download path thereof based on described configuration information; Each software package title that in described first determining step, determined software package comprises is determined according to comps file; Download step, downloads the software package corresponding with determined software package title in described first determining step and described second determining step; Foundation step, creates yum software storage based on downloaded software package; Distribution steps, performs follow-up distribution based on created yum warehouse and makes process.The distribution that the method can facilitate research staff to carry out the (SuSE) Linux OS of customization makes.
Description
Technical field
The present invention relates to (SuSE) Linux OS field, particularly relate to making distribution (generation) field of (SuSE) Linux OS, specifically, relate to a kind of (SuSE) Linux OS distribution method for making.
Background technology
Usually, the distribution of (SuSE) Linux OS makes to have been come by pungi instrument.Pungi can issue according to configuration file ks.cfg the (SuSE) Linux OS making latest edition.
Carry out simple declaration below in conjunction with Fig. 1 and utilize pungi to issue the process making (SuSE) Linux OS.
Step S110, resolves ks.cfg file, and obtain software package group name and claim the set A with software package title, software package group name now claims all not comprise version information with software package title;
Step S120, increases software package core and the software package base of pungi program default installation in set A;
Step S130, by comps file to the definition of software package and software package, launch all software packages, obtain the software package list of the software package defined in comps file;
Step S140, the interface being obtained up-to-date software package by yum selects the software package of latest edition inside server warehouse.
Step S150, downloads to catalogue/var/cache/pungi that operating system production environment is specified by up-to-date software package.
Step S160, according to directory A, creates yum warehouse.
But (SuSE) Linux OS manufacturer all wishes the operating system making current the researched and developed latest edition of distribution in not all situation.In some cases, what buy desired by client is not up-to-date (SuSE) Linux OS, but certain particular version that (SuSE) Linux OS manufacturer formulates according to different customer demand.Such as, the requirement that (SuSE) Linux OS manufacturer understands each client develops version software bag package1, and current package1 has three serial versions: 1.1.1,1.1.2,1.1.3; 1.2.1,1.2.2,1.2.3; 1.3.1,1.3.2,1.3.3,1.3.4.Suppose in the version of these three systems, 1.3.4 is the current latest edition of this software package.But 1.1.1,1.1.2,1.1.3 are be the version that client C1 customizes specially, 1.2.1,1.2.2,1.2.3 are be the version that client C2 customizes specially, and 1.3.1,1.3.2,1.3.3,1.3.4 are not all suitable for client C1 or C2.Like this, the latest edition required for client C1 and C2 is not the actual latest edition of software package package1, is respectively 1.1.3 and 1.2.3 to the latest edition of client C1 and C2, package1.In this case, traditional pungi technology then cannot correctly for client C1 or C2 issues the (SuSE) Linux OS making and comprise right version software package package1.
In brief, traditional pungi is utilized cannot to meet preferably for client issues the (SuSE) Linux OS making particular version.
Summary of the invention
One of technical matters to be solved by this invention needs to provide a kind of a large amount of manually operated (SuSE) Linux OS distribution method for making because avoiding because customization brings.
In order to solve the problems of the technologies described above, the invention provides a kind of (SuSE) Linux OS distribution method for making.The method comprises:
First determining step, obtains the configuration information about software package, software package and their download path, determines that each software package group name claims and download path and each software package title and download path thereof based on described configuration information.
Second determining step, determines according to comps file each software package title that in described first determining step, determined software package comprises;
Download step, downloads the software package corresponding with determined software package title in described first determining step and described second determining step;
Foundation step, creates yum software storage based on downloaded software package;
Distribution steps, performs follow-up distribution based on created yum warehouse and makes process.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, described configuration information also comprises the information whether wanting update software package base and software package core.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, in described first determining step, also comprises the version information of version information that each software package group name claims and/or each software package in described configuration information; And to claim based on each software package group name that described configuration information determines to comprise version information and/or the title of each software package.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, in described download step, for the software package comprising version information in software package title, downloads the software package with the corresponding version of version information in software package title; And, for the software package not comprising version information in software package title, download the software package of latest edition.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, is kept at described configuration information in ks.cfg file.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, also comprises, judges whether there is the software package title containing version information in determined each software package title in described first determining step; And, if judged result is for existing, utilizes yum to rely on and checking interface, detect the software package downloaded in described download step and whether meet dependence required by successful installing operating system.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, if be detected as the dependence do not met required by successful installing operating system, then point out about the reason not meeting dependence thus cause (SuSE) Linux OS distribution to make failed information, and ending process.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, whether the software package downloaded in the described download step of detection meets in the process of the dependence required by successful installing operating system, according to the layer residing for each software package, each software package that described download step is downloaded is sorted, obtain software package list; And to detect one by one for sorted software package list and whether downloaded whole software packages that each software package relies on.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, whether the software package downloaded in the described download step of detection meets in the process of the dependence required by successful installing operating system, according to the layer residing for each software package, each software package that described download step is downloaded is sorted, obtain software package list; And whether preferential detection has downloaded the whole software packages being in high-rise software package and relying on.
(SuSE) Linux OS distribution method for making according to a further aspect of the invention, realizes this method by the process relevant to the bag collection stage in the production run of amendment pungi.
Compared with prior art, one or more embodiment of the present invention can have the following advantages by tool:
By determining that based on described configuration information each software package group name claims and download path and each software package title and download path thereof, the distribution that research staff can be facilitated to carry out the customization of (SuSE) Linux OS makes, and avoids a large amount of manual operations because customization brings.
An aspect of of the present present invention is considered when customization, might not expect that software package base and software package core is upgraded to latest edition, even, software package base and the software package core of the latest edition version that might not customize with client is mutually compatible sometimes.Therefore, the present invention is based on and comprise the configuration informations such as the information of whether wanting update software package base and software package core to download corresponding version, and carry out dependence detection according to the version that configuration information is downloaded, effectively can save the version issuing date of research staff, avoid the version of too much manual operation or distribution unavailable.
Other advantages of the present invention, target, to set forth in the following description to a certain extent with feature, and to a certain extent, based on will be apparent to those skilled in the art to investigating hereafter, or can be instructed from the practice of the present invention.Target of the present invention and other advantages can by instructionss below, claims, and in accompanying drawing, specifically noted structure realizes and obtains.
Accompanying drawing explanation
Accompanying drawing is used to provide a further understanding of the present invention, and forms a part for instructions, with embodiments of the invention jointly for explaining the present invention, is not construed as limiting the invention.In the accompanying drawings:
Fig. 1 is that prior art utilizes pungi to issue the process making (SuSE) Linux OS;
Fig. 2 is the process flow diagram of (SuSE) Linux OS distribution method for making according to a first embodiment of the present invention;
Fig. 3 is (SuSE) Linux OS layer architecture schematic diagram.
Embodiment
Describe embodiments of the present invention in detail below with reference to drawings and Examples, to the present invention, how application technology means solve technical matters whereby, and the implementation procedure reaching technique effect can fully understand and implement according to this.It should be noted that, only otherwise form conflict, each embodiment in the present invention and each feature in each embodiment can be combined with each other, and the technical scheme formed is all within protection scope of the present invention.
first embodiment
Each step of the (SuSE) Linux OS distribution method for making according to the present embodiment is described in detail below with reference to Fig. 2.
Step S210, obtains the configuration information about software package, software package and their download path, determines that each software package group name claims and download path and each software package title and download path thereof based on this configuration information;
Preferably, configuration information also comprises the information whether wanting update software package base and software package core.Like this, flexible configuration can be carried out according to configuration information and whether want update software package base and software package core.
In conventional art, all can obtain up-to-date software package base and software package core at every turn, but under the occasion of customization, might not expect that software package base and software package core is upgraded to latest edition, even, sometimes software package base and the software package core of the latest edition version that might not customize with client is mutually compatible, and therefore, the method for the present embodiment can meet Customization demand better.
Be preferably, configuration information comprises the version information of version information that each software package group name claims and/or each software package, comprises each software package group name claims and/or the configuration information of version information of each software package determines to comprise version information each software package group name claim and/or the title of each software package based on this.In linux system, also the software package title/software package group name comprising version information is called software package full name/software package full name.
Step S220, according to each software package title that the software package determined in comps file determining step S210 comprises.To be described in detail to comps file follow-up.
Step S230, download the software package corresponding with the software package title determined in above-mentioned steps S210 and S220, further, for the software package comprising version information in software package title, download the software package with the corresponding version of version information in software package title, for the software package not comprising version information in software package title, download the software package of latest edition.
Step S240, the software package downloaded based on step S230 creates yum software storage.
Alternatively, the (SuSE) Linux OS distribution method for making of the present embodiment can comprise step S250.
In step s 250, in determining step S210, in determined each software package title, whether there is the software package title containing version information, if be judged as existing, then enter step S260, if the judgment is No, then enter step S270.
It should be noted that the (SuSE) Linux OS distribution method for making of the present embodiment also can not comprise step S250 and directly enter step S270 from step S240.
Step S260, utilize yum to rely on and check interface, whether the software package downloaded in detecting step S230 meets the dependence required by successful installing operating system, if testing result is satisfied, then enters step S270, otherwise, then enter step S280.
The present embodiment, by performing the dependence check processing of rapid S260, can be avoided not mating due to the software package version in configuration information or version configuration error causes cannot issue and make the disabled situation of operating system that operating system or institute issue making preferably.
Step S270, performs follow-up distribution based on created yum warehouse and makes process.
Step S280, ends process.Preferably, point out about the reason not meeting dependence thus cause (SuSE) Linux OS distribution to make failed information, and ending process.Like this, technician can analyze the failed reason of distribution making, reset above-mentioned configuration information according to the suggested information about the reason not meeting dependence.The non-existent information of certain other software package of certain software package dependence generally can be shown as about the reason not meeting dependence.
In addition, in step S210, configuration information can be set by the ks.cfg in amendment (SuSE) Linux OS, in other words, configuration information is kept in ks.cfg file, can determines that each software package group name claims and each software package title based on amended ks.cfg like this.
The following detailed description of relying on the principle checked in (SuSE) Linux OS about software package.Rely on and check and first need to understand the composition that Linux issues version operating system introducing software package.(SuSE) Linux OS framework roughly as shown in Figure 3.
The roughly formation that Linux issues version can be understood by the framework shown in Fig. 3.Application program (Application) is by operation third party software interface library (Third Libary) and base library (glibc) as we can see from the figure, come off-line operation linux kernel (Linux Kernel) and hardware drive program (Driver), by kernel (Linux Kernel) with use hardware resource (Hardware) at hardware foundation (Hardware).
The present inventor notices that the dependence of each software package is a kind of top-down dependence.More specifically, when the software package being in application software layer can normally use, third party software storehouse and the base library of lower floor must be relied on, and kernel and driver.Therefore, can draw a conclusion, the dependence being exactly software package is unidirectional, and non-bidirectional.Assuming that software package A, B, C, D are in application software layer, third party software storehouse, base library, kernel respectively.So, its dependence is as follows:
The first, A software package relies on B, C, D.
The second, B software package relies on C, D.
Three, C software package relies on D.
Four, D software package does not rely on any software package.
Based on above-mentioned consideration, in step S260, when utilizing yum dependence to check whether the software package downloaded in interface detecting step S230 meets the dependence required by successful installing operating system, specifically comprise, first according to the layer residing for each software package, each software package that step S230 downloads is sorted, obtain software package list.Then detect one by one for sorted software package and whether downloaded whole software packages that each software package relies on.Like this, once the software package that certain software package relies on is not downloaded in discovery, then make the testing result of step S260 for not meet.In a kind of optimal way, can sort by the layer residing for Linux framework from high level to bottom, according to the software package list from high level to low layer, whether preferential detection has downloaded the whole software packages being in high-rise software package and relying on.In this fashion, because the dependence being in high-rise software package is more complicated more assorted, in addition, generally, the software package of customization is generally also in high level, high-rise software package dependency relationship is more easily made mistakes, and therefore preferred detection is in the dependence (namely whether preferential detection has downloaded whole software packages that this software package relies on) of high-rise software package, is conducive to detecting the dependence problem that may exist quickly.
It should be noted that, the above steps of the present embodiment can be realized by amendment pungi.Main amendment is embodied in process relevant to the bag collection stage in the production run of amendment pungi, and such as, amendment pungi collects the stage of software package, the obtain manner of amendment indicated release software package and checks the closed dependence that all bags carry out.
Simply introduce the content format of ks.cfg file below, illustrate roughly as follows:
In example by this ks.cfg above, main contents can be divided into two pieces:
First piece, be exactly the acquisition address of designated software bag, namely " repo – name=A--baseurl=B " OK, its implication be specify software package obtain source, warehouse B, and these software packages are downloaded in the catalogue of local name/var/cache/pungi/A, word string implication description below:
A: the name that user writes arbitrarily.
B: the address of depositing all software packages producing iso.
Second piece is exactly designated software package and software package.Wherein %packages and %end specifies software package to be obtained and the beginning of software package and the mark of end, and this is marked at when pungi resolves ks.cfg and uses.Word string@core ,@base, package1, package2 is also there is in the region that %packages and %end comprises.Its implication is described below:
@core:core software package, i.e. one group of software package set, define these software packages and comprise which software package in comps file, and the title of each software package.
@base:base software package, i.e. one group of software package set, define these software packages and comprise which software package in comps file, and the title of each software package.
Package1: software package title, in the title of these software packages of comps document definition, function and affiliated grouping and purposes.
Package2: software package title, in title and the affiliated grouping of these software packages of comps document definition.
Do a simple declaration to comps file more below, first comps is XML shelves forms, about content format, is exemplified below:
By the example of the above-mentioned comps file, its content format can be described clearly, here, can revise arbitrarily comps file, to add the software package of customization.
Those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, they can be stored and be performed by calculation element in the storage device, or they are made into each integrated circuit modules respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
Although the embodiment disclosed by the present invention is as above, the embodiment that described content just adopts for the ease of understanding the present invention, and be not used to limit the present invention.Technician in any the technical field of the invention; under the prerequisite not departing from the spirit and scope disclosed by the present invention; any amendment and change can be done what implement in form and in details; but scope of patent protection of the present invention, the scope that still must define with appending claims is as the criterion.
Claims (9)
1. a (SuSE) Linux OS distribution method for making, is characterized in that, comprising:
First determining step, obtains the configuration information about software package, software package and their download path, determines that each software package group name claims and download path and each software package title and download path thereof based on described configuration information;
Second determining step, determines according to comps file each software package title that in described first determining step, determined software package comprises;
Download step, downloads the software package corresponding with determined software package title in described first determining step and described second determining step;
Foundation step, creates yum software storage based on downloaded software package;
Distribution steps, performs follow-up distribution based on created described yum software storage and makes process;
In described download step, for the software package comprising version information in software package title, download the software package with the corresponding version of version information in software package title; And, for the software package not comprising version information in software package title, download the software package of latest edition.
2. method according to claim 1, is characterized in that,
Whether described configuration information also comprises wants update software package substantially to organize the information with software package core group.
3. method according to claim 1, is characterized in that, in described first determining step,
The version information of version information that each software package group name claims and/or each software package is also comprised in described configuration information; And
The each software package group name determining to comprise version information based on described configuration information claims and/or the title of each software package.
4. method according to claim 1, is characterized in that, is kept in ks.cfg file by described configuration information.
5. method according to any one of claim 1 to 4, is characterized in that, also comprises,
Judge whether there is the software package title containing version information in determined each software package title in described first determining step; And,
If judged result is for existing, utilizes yum to rely on and checking interface, detect the software package downloaded in described download step and whether meet dependence required by successful installing operating system.
6. method according to claim 5, is characterized in that, also comprises,
If be detected as the dependence do not met required by successful installing operating system, then point out about the reason not meeting dependence thus cause (SuSE) Linux OS distribution to make failed information, and ending process.
7. method according to claim 5, is characterized in that, whether the software package downloaded in the described download step of detection meets in the process of the dependence required by successful installing operating system,
According to the layer residing for each software package, each software package that described download step is downloaded is sorted, obtain software package list; And
Detect one by one for sorted software package list and whether downloaded whole software packages that each software package relies on.
8. method according to claim 7, is characterized in that, whether the software package downloaded in the described download step of detection meets in the process of the dependence required by successful installing operating system,
According to the layer residing for each software package, each software package that described download step is downloaded is sorted, obtain software package list;
And
Whether preferential detection has downloaded the whole software packages being in high-rise software package and relying on.
9. method according to claim 1, is characterized in that, realizes this method by the process relevant to the bag collection stage in the production run of amendment pungi.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210137397.XA CN102654835B (en) | 2012-05-03 | 2012-05-03 | (SuSE) Linux OS distribution method for making |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210137397.XA CN102654835B (en) | 2012-05-03 | 2012-05-03 | (SuSE) Linux OS distribution method for making |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102654835A CN102654835A (en) | 2012-09-05 |
| CN102654835B true CN102654835B (en) | 2015-10-07 |
Family
ID=46730461
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210137397.XA Active CN102654835B (en) | 2012-05-03 | 2012-05-03 | (SuSE) Linux OS distribution method for making |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102654835B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2018503182A (en) * | 2014-12-12 | 2018-02-01 | エイブル ワールド インターナショナル リミテッド | Method for providing network service and network service station using said method |
| CN106484458B (en) * | 2016-09-08 | 2020-02-21 | 上海斐讯数据通信技术有限公司 | Open type software warehouse management system and management method thereof |
| CN112230976B (en) * | 2020-09-01 | 2023-07-18 | 麒麟软件有限公司 | Method for simultaneously supporting two software package managers and supporting software package interdependence and conflict detection |
| CN113342377A (en) * | 2021-06-23 | 2021-09-03 | 深圳兆日科技股份有限公司 | Third-party software package backup method and device and computer readable storage medium |
| CN114070846A (en) * | 2021-11-25 | 2022-02-18 | 安天科技集团股份有限公司 | Synchronization method and device for software package warehouse under Linux operating system |
| CN114443687B (en) * | 2021-12-23 | 2024-02-27 | 苏州浪潮智能科技有限公司 | Software package custom system for constructing operating system image and application method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1621997A1 (en) * | 2003-05-08 | 2006-02-01 | Fujitsu Limited | Software configuration restoration method and device, and computer-readable recording medium |
| CN101334729A (en) * | 2008-08-07 | 2008-12-31 | 金蝶软件（中国）有限公司 | Method and device for treating the software package |
| CN102129381A (en) * | 2011-03-14 | 2011-07-20 | 兰雨晴 | Method for customizing linux operating system |
-
2012
- 2012-05-03 CN CN201210137397.XA patent/CN102654835B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1621997A1 (en) * | 2003-05-08 | 2006-02-01 | Fujitsu Limited | Software configuration restoration method and device, and computer-readable recording medium |
| CN101334729A (en) * | 2008-08-07 | 2008-12-31 | 金蝶软件（中国）有限公司 | Method and device for treating the software package |
| CN102129381A (en) * | 2011-03-14 | 2011-07-20 | 兰雨晴 | Method for customizing linux operating system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102654835A (en) | 2012-09-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102654835B (en) | (SuSE) Linux OS distribution method for making | |
| US10157068B2 (en) | Configuring and operating applications using a descriptor | |
| US9274811B1 (en) | System and method for cloud provisioning and application deployment | |
| EP2562641B1 (en) | Software application porting system | |
| US20100070961A1 (en) | Supplying Software Updates Synchronously | |
| CN103324474B (en) | Based on (SuSE) Linux OS across the method for System structure ISO and module | |
| US9442708B1 (en) | System and method for installing, updating and uninstalling applications | |
| US20240223471A1 (en) | Standardized format for containerized applications | |
| CN102982169B (en) | Browser and method for isolating webpage plugins | |
| CN102541596A (en) | Operating system upgrading method and device | |
| CN105159788B (en) | Method and system for dynamically sharing resources between Android applications | |
| AU2008296957A1 (en) | Bootstrapper and software download manager | |
| US20080201703A1 (en) | Packaging content updates | |
| CN107025108B (en) | Exporting hierarchical data from a Source Code Management (SCM) system to a Product Lifecycle Management (PLM) system | |
| CN107038519B (en) | Method and system for bidirectional data synchronization between systems | |
| US20060235928A1 (en) | System and method for creating a mapping document for binding messages between an application and an associated backend server | |
| CN104765816B (en) | Browser upgrading method and device and electronic equipment | |
| US11900089B2 (en) | Automatically configuring and deploying a software operator in a distributed computing environment from a package | |
| CN105653335A (en) | Plug-in procedure control method and device | |
| US20220137944A1 (en) | Accelerating application and sub-package installations | |
| US7890945B2 (en) | Method for versioning classes loaded in an OSGi-enabled J2EE environment | |
| CN114968406B (en) | Plug-in management method and device, electronic equipment and storage medium | |
| CN105630547A (en) | Patch program installing method and patch program installing device | |
| JP6817030B2 (en) | Hierarchical data export from Product Lifecycle Management (PLM) system to Source Code Management (SCM) system | |
| CN101162954B (en) | Method of upgrading software by using common module shared by multiple models, and digital broadcast receiver therefor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |