CN100399267C - Method of managing software installation and unloading - Google Patents
Method of managing software installation and unloading Download PDFInfo
- Publication number
- CN100399267C CN100399267C CNB2005100554997A CN200510055499A CN100399267C CN 100399267 C CN100399267 C CN 100399267C CN B2005100554997 A CNB2005100554997 A CN B2005100554997A CN 200510055499 A CN200510055499 A CN 200510055499A CN 100399267 C CN100399267 C CN 100399267C
- Authority
- CN
- China
- Prior art keywords
- software
- user side
- installation
- assembly
- install
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The present invention discloses a method of managing software installation and un-installation. A local software information library is prearranged at a user end to store information description files of installed software dependence relation. When the software or components in the software are uninstalled, the user end can judge whether a software depending on the software to be uninstalled exists according to the stored information description files of the installed software dependence relations in the local software information library. If does, the software is not uninstalled; if not, the software is uninstalled. The present invention also arranges information description files of the software dependence relation in a software installation unit for providing installation programs. When the software or components in the software are installed, the user end can determine whether normal running of the installed software depends on other software according to the information description file of the software dependence relation obtained from the installation unit; if does, after other software which is depended on is installed by the user end, the software or components to be installed are installed.
Description
Technical field
The present invention relates to software installation/Unloading Technology in the computer system, particularly a kind of method of management software installation/unloading.
Background technology
In a computer system, tend to install various types of computer softwares, to adapt to the different demands of different user.Exist dependence between these softwares probably, promptly some software must depend on the normally operation of other softwares.This just requires in install software, other softwares that must at first this software be installed and be relied on.Equally, in uninstall, also unloading earlier depends on other softwares of this software, otherwise, can cause other softwares that depend on this software normally to move after unloading this software.
At present, software can be divided three classes to the management of self installing.The first kind is not considered the dependence between the software in software installation process, direct install software, but institute's installed software may can't normally be moved because lacking the software that is relied on.Second class, the supervisory routine of software to self is set in install software in advance, the supervisory routine of software self is checked the software whether user side exists this software to rely in software installation process, if exist, this software is installed directly then, if there is no, then send information to user side, by user side the software that this software relies on is installed after, this software is installed again, but must need the client of user side to participate in this software installation process, increase the trouble of client's install software.The 3rd class, supervisory routine and the installation procedure of this software institute depended software or the source-information of this software institute depended software installation procedure of software to self is set in install software in advance, the supervisory routine of software self is checked the software whether user side exists this software to rely in software installation process, if exist, this software then directly is installed, if there is no, then according to source-information that is arranged on this software institute depended software program in the install software or the direct mount message that from install software, obtains this software, after the software that this software relies on is installed, this software is installed again, but need in this software installation process supervisory routine of software to self additionally to be set again to each software, and the source-information of the installation procedure of this software institute depended software or this software institute depended software installation procedure, this has not only increased the storage space that install software takies, and is provided with more loaded down with trivial details to each install software.
Further, not to the management of software unloading, can't carry out the judgement of software dependence at present,, then can cause other softwares normally to move if unloaded the software that other software relies on to the software that will unload.
Therefore, how software with software dependence is installed on the basis that does not increase software memory space easily, and unloading has the software of software dependence, and other softwares that do not cause this software and depend on this software can't normally move and do not become problem demanding prompt solution.
Summary of the invention
In view of this, fundamental purpose of the present invention is to provide a kind of method of management software installation/unloading, this method not only can be installed the software with software dependence easily on the basis that does not increase software memory space, assurance institute install software is normally moved, and when unloading has the software of software dependence, guarantee that other softwares in the user side normally move.
According to above-mentioned purpose, technical scheme of the present invention is achieved in that
Software dependency information description document is set, described file comprises: the component software and the version of the required dependence of normal operation of the software of the required dependence of normal operation of software and version, software, this method also comprises: when install software, user side judges whether to exist the software of wanting install software to rely on according to the software dependency information description document that is provided with, if exist, user side is installed the software that is relied on earlier, installs and wants install software; Otherwise user side is installed and is wanted install software; Described user side is installed the software process that is relied on earlier: the user side setting provides the software administration service unit of pre-mounting interface, the software installation unit that is used for the storing software installation procedure calls the pre-mounting interface of software administration service unit, is obtained by the installation procedure of depended software by the software administration service unit and also installs by depended software; Perhaps want the installation procedure of install software to obtain, install by depended software by the installation procedure of depended software by user side;
When uninstall, user side judges whether to exist according to the software dependency information description document that is provided with and depends on the software of wanting uninstall, if exist, user side not uninstall or the user side software that will unload and the software that depends on institute's uninstall all unloads; Otherwise, the software that the user side unloading will unload;
The dependency information description document of wanting uninstall and depending on the software correspondence of institute's uninstall that user side will be arranged in the local software information bank is deleted.
When uninstall, user side judges whether to exist according to the software dependency information description document that is provided with and depends on the software of wanting uninstall, if exist, user side not uninstall or the user side software that will unload and the software that depends on institute's uninstall all unloads; Otherwise, the software that the user side unloading will unload.
Described software dependency information description document is a user side during the dependency information description document of install software, and this document is stored in the local software information bank that user side is provided with.
Described software dependency information description document is a user side not during the dependency information description document of install software, and this document is stored in to be provided in the software of the software installation procedure installation unit.
After described user side was installed by depended software earlier, this method further comprised:
User side will be kept in the local software information bank of setting by the dependency information description document of depended software, and be labeled as passive installation;
After install software was wanted in described installation, this method further comprised: user side is kept at the dependency information description document of software in the local software information bank of setting, and is labeled as initiatively installation.
This method further comprises:
User side judge want uninstall with depend on institute's uninstall whether software relied on be labeled as passive installed software and also relied on by mounted other software of user side, if there is no depend on other software of this passive install software, user side unloads this and is labeled as passive installed software, and the dependency information description document that will be arranged on this passive install software in the local software information bank is deleted; Otherwise user side does not process, and finishes.
Described software is the software with one or more assemblies.
When software was made amendment, this method further comprised:
Software increases assembly, user side judges according to the software dependency information description document that assembly is set whether user side has installed software and the assembly of wanting installation component to rely on, if do not install, user side is installed software and the assembly that is relied on earlier, installs and wants installation component; Otherwise user side is installed and is wanted installation component;
When the unloading assembly, user side is judged according to the software dependency information description document that assembly is set whether user side exists and is depended on the software and the assembly that will unload assembly, if exist, user side does not unload will unload the assembly that assembly or user side will unload and depend on the software and the assembly that will unload assembly and all unloads; Otherwise, the assembly that the user side unloading will unload.
From such scheme as can be seen, the present invention sets in advance at user side and is used to store the local software information bank of install software dependency information description document, during assembly in wanting uninstall or software, user side can judge whether to exist and depend on the software of wanting uninstall according to the dependency information of the install software description document of local software information bank storage, if have, uninstall not then; Otherwise, uninstall.Therefore, when method provided by the invention has the software of software dependence in unloading, guarantee that other softwares that rely on the uninstall of wanting normally move.The present invention also is provided with software dependency information description document at the software installation unit that installation procedure is provided, when the assembly of install software or software, user side can determine whether the normal operation of institute's install software depends on other softwares according to the software dependency information description document of obtaining from installation unit, if, after user side can be installed other softwares that relied on earlier, install again and want installed software or assembly.Because the present invention will be provided with the program that management software is installed in software installation procedure unlike prior art, also can not be provided with by depended software, saved the space, so the present invention installs the software with software dependence easily on the basis that does not increase software memory space, assurance institute install software is normally moved.
Description of drawings
The Governance framework figure that Fig. 1 installs/unloads for software of the present invention;
Fig. 2 is the method specific embodiment synoptic diagram of management software installation/unloading of the present invention.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, below lift specific embodiment and, the present invention is further elaborated with reference to accompanying drawing.
Method provided by the invention can be in software installation process, directly judge whether to need to install the software that this software relied on by user side, if desired, behind the software of then this software being installed and being relied on this software is installed again; If do not need, this software is installed directly then.Method provided by the invention can also be in the software uninstall process, directly judge whether to have in the computer system and depend on the software of wanting uninstall by user side, if exist, then point out the user whether simultaneously uninstall and depend on the software of wanting uninstall, perhaps point out the user not unload this software, otherwise, directly unload this software.
Method provided by the invention can also be revised each assembly in the install software, promptly at each assembly in the install software, judges whether to need to install or unload other softwares or assembly.
The Governance framework figure that Fig. 1 installs/unloads for software of the present invention, this Governance framework comprises: the software installation unit 100 with software installation/Uninstaller and software dependency information, in user side, software installation/unloading management service unit 101 and have the local software information bank 102 of the dependency information of install software.
Software installation/unloading management service unit 101 in the user side is parts of being actually responsible for management software installation/uninstall process, this unit provides three interfaces for software installation unit 100: pre-mounting interface, unload interface and revise interface in advance in advance, use in software installation process, uninstall process and modification process for software installation unit 100 respectively.When software installation unit 100 carries out information interaction by these three interfaces and software installation/unloading management service unit 101, judge by the 101 pairs of software dependences in software installation/unloading management service unit, install or unload the relevant component software that is relied on of relevant institute's depended software and installation or unloading.
In software installation and modification process, software installation unit 100 need provide a description the software dependency information, so that software administration service unit 101 upgrades the dependency information of local software information banks 102 softwares of preserving.In the software uninstall process, software administration service unit 101 directly obtains the dependency information of this software from local software information bank 102.
Be used to preserve the dependency information of install software in the local software information bank 102 among the present invention, in local software information bank 102, the mark of install software be divided into initiatively install and passive installation two classes.Wherein, be labeled as initiatively installed software be meant user side initiatively the operating software installation procedure finish installed software; Being labeled as passive installed software is meant owing to being relied on by required install software by software installation/unloading management service unit 101 passive installed software.
The dependency information of software can be stored in the dependency information description document of software, and the dependency information description document with software is stored in software installation unit 100 or/and in the local software information bank 102 again.The dependency information of software comprises: the component software and the version thereof of the required dependence of normal operation of the software of the required dependence of normal operation of this software and version thereof, this software.
Below respectively software administration service unit 101 being carried out each process is described in detail.
1, the pre-installation process of software
The pre-installation of software is meant when a software depends on other softwares promptly have only normally operation of this software when other softwares exist, by the process of software administration service unit 101 installation other softwares that this software relied on.
Software administration service unit 101 provides pre-mounting interface for software installation unit 100, and software installation unit 100 provides the dependency information description document of saved software in advance for software administration service unit 101 by this interface.Software administration service unit 101 judges whether the software that this software relies on is installed at user side after receiving the dependency information description document of software, and judge that whether installation is by the version of depended software by the version of depended software in the dependency information description document of software, if what be not mounted or installed by depended software is not by the version of depended software by the version of depended software in the dependency information description document of software, then pass through certain predefined mode by software administration service unit 101, as pass through computer network, obtain this by the installation procedure of depended software, after installation, to be kept in the local software information bank 102 by the software dependency information description document of depended software, after being passive installation with tense marker by depended software, continue to install this software, the software dependency information description document of this software is kept at local software information bank 102, is labeled as simultaneously initiatively and installs.If the version that has been mounted and has been installed by depended software by depended software be in the dependency information description document of software by the version of depended software, then software administration service unit 101 is directly installed this software.
There is not successful installation if get access to by depended software or by depended software by certain predefined mode, then software administration service unit 101 selects by the user whether this software is installed after sending information, and perhaps this software is not directly installed in management service unit 101.
2, the pre-uninstall process of software
The pre-uninstall process of software is in the process of software unloading, whether all software dependency information description document inspections of being preserved according to local software information bank 102 by software administration service unit 101 exist other softwares that depend on this software, and unloading depends on other softwares of this software.
Software administration service unit 101 provides pre-unloading interface for software installation unit 100, and software installation unit 100 calls pre-unloading interface in the process of uninstall, is depended on other software of this software by 101 unloadings of software administration service unit.
In the process of software unloading, at first software administration service unit 101 judges whether to exist other softwares that depend on this software, if there is no, then obtains the software Uninstaller from software installation unit 100, directly unloads this software.If existence, then other softwares that whether unload this software simultaneously and depend on this software by user's selection.If the user selects not unload, then do not unload this software, finish uninstall process.If the user selects unloading, then software administration service unit 101 is finished the process that unloading this software and unloading depend on other softwares of this software, and the dependency information description document that is kept at this software in the local software information bank 102 and depends on other software correspondences of this software is deleted.
Before this software in will being kept at local software information bank 102 and the dependency information description document that depends on other software of this software are deleted, software administration service unit 101 judges according to the dependency information description document of these softwares (other software that comprises this software and depend on this software) whether the passive install software that this software relies on is still relied on by other softwares and assembly, if not, then software administration service unit 101 is deleted these passive installed software, and the dependence information description file of these passive installed software correspondences in the deletion local software information bank 102, if then do not delete these passive installed software.
3, the pre-modification of software
Software can increase some assembly of installing or delete in the software in modification/reparation installation process.The pre-modification of software is meant in this course, and software administration service unit 101 is pre-installs other softwares or the assemblies that this assembly relied on, or the passive install software that no longer relied on of pre-unloading or the process of assembly.
Software administration service unit 101 provides pre-modification interface for the pre-modification of software, when software installation unit 100 carries out the pre-modification of software by this interface, must provide the dependency information description document that increases or delete the assembly correspondence.Software administration service unit 101 can be finished pre-installation or pre-uninstall process according to the software dependency information description document that increases or delete the assembly correspondence.
When increasing certain assembly, software administration service unit 101 can check whether other softwares or assembly that this assembly relied on have been installed, if there is no be mounted by depended software or assembly or by depended software, then software administration service unit 101 is installed this assembly, and the software dependency information description document of in local software information bank 102, storing this assembly, be labeled as initiatively installation component; If exist certain not to be mounted by depended software or assembly, then software administration service unit 101 is installed software or the assembly that is relied on earlier, and in local software information bank 102, store by the dependency information description document of depended software or assembly, be labeled as passive installation component or software, software administration service unit 101 is installed this assembly then, and the dependency information description document of in local software information bank 102, storing this assembly, be labeled as initiatively installation component.
When certain assembly of deletion, then software administration service unit 101 can check that the software in the local software information bank 102 relies on the information description file, judges whether to depend on other assemblies or the software of this assembly, if having, then can not delete this assembly; If do not have, then software administration service unit 101 is deleted these assemblies, and the software of this assembly correspondence relies on the information description file in the deletion local software information bank 102, then, software administration service unit 101 checks whether passive installed software or assembly that this assembly relied on are still relied on by other softwares and assembly, if not, then software administration service unit 101 is deleted these passive installed software or assemblies, and the software of these passive installed software or assembly correspondence relies on the information description file in the deletion local software information bank 102, if then do not delete these passive installed software or assemblies.
Lift a specific embodiment explanation the present invention.
Fig. 2 is the method specific embodiment synoptic diagram of management software installation/unloading of the present invention.Suppose to have five software A, B, C, D and E, wherein software A is made of three assembly A1, A2 and A3, dependence between these five softwares is: the assembly A1 among the software A depends on software B, assembly A2 among the software A depends on software C, assembly A3 among the software A depends on software D, and software E depends on software B.
Suppose at user side software E and software B to be installed, wherein, software E is an initiatively installed software of user side, and promptly marking software E initiatively installs in local software information bank 102; Software B is that software administration service unit 101 is installed in pre-installation process, and promptly mark B software is passive installation in local software information bank 102.
The installation process of software A is as described below.
Suppose that the user selects assembly A1 and the assembly A2 of install software A, then software installation unit 100 by and software administration service unit 101 between pre-mounting interface, finish following steps:
Step 10, software administration service unit 101 determine that according to the dependency information description document of software A software A wants the mounting portion to depend on software B and software C.
Step 11, software administration service unit 101 are checked user side installed software, and the discovery user side has been installed software B, does not then need install software B once more.
Step 12, software administration service unit 101 are checked user side installed software, find that user side does not have install software C, then from the network of software installation unit or computer system, obtain the installation procedure of software C, install software C, and the dependency information description document of software C stored in the local software information bank 102, be labeled as passive installation.
Step 13, software administration service unit 101 install software A want the mounting portion, i.e. the assembly A1 of software A and assembly A2, and the dependency information description document of assembly A1 and assembly A2 stored in the local software information bank 102, be labeled as initiatively and install.
The process of the mounting portion of modification software A is as described below.
Suppose to increase the assembly A3 of software A, then software installation unit 100 by and software administration service unit 101 between pre-modification interface, finish following steps:
Step 20, software administration service unit 101 determine that according to the dependence information description file of assembly A3 A3 depends on software D.
Step 21, software administration service unit 101 are checked user side installed software, find that user side does not have install software D, then from the network of software installation unit or computer system, obtain the installation procedure of software D, install software D, and the dependency information description document of software D stored in the local software information bank 102, be labeled as passive installation.
Step 22, software administration service unit 101 installing software component A3, and the dependency information description document of assembly A3 stored in the local software information bank 102, be labeled as initiatively and install.
Suppose to delete the assembly A2 of A software, then software installation unit 100 by and software administration service unit 101 between pre-modification interface, finish following steps:
Step 30, software administration service unit 101 check whether local software information bank 102 exists other softwares or the assembly that depends on assembly A2, and finding does not have such assembly or software, then unloads assembly A2.
Behind step 31, the software administration service unit 101 unloading assembly A2, when removing the software dependency information description document of the assembly A2 that preserves in the local software information bank 102, obtain software and the component list that the assembly A2 in the dependency information description document is relied on.
Step 32, software administration service unit 101 are checked software and the component list that assembly A2 is relied on, determine the software C that assembly A2 is relied on, determine that according to institute's saved software dependency information description document in the local software information bank 102 software C is passive installation and other softwares that do not depend on software C, software administration service unit 101 uninstall C, and the dependency information description document of the software C in the removing local software information bank 102.
The process of uninstall A is as described below.
Step 40, software administration service unit 101 are according to institute's saved software dependency information description document in the local software information bank 102, determine whether to depend on other softwares of software A, discovery does not have such software, uninstall A then, when removing the dependency information description document of the software A that preserves in the local software information bank 102, obtain software and the component list that the software A in the dependency information description document is relied on.
Step 41, software administration service unit 101 are checked software and the component list that software A is relied on, determine software B, C, D that software A is relied on, determine that according to checking the dependency information description document in the local software information bank 102 software C and software D are passive installation and do not depend on software C and other softwares of software D, software administration service unit 101 uninstall C and software D, and the software C in the removing local software information bank 102 and the dependency information description document of software D correspondence; Determine that according to the dependency information description document in the inspection local software information bank 102 software B is relied on by user side install software E, so can not uninstall B.
After supposing uninstall A, also want uninstall B, then software administration service unit 101 is finished following steps:
Whether simultaneously step 50, software administration service unit 101 are checked local software information bank 102, determine that then software E depends on software B, then point out the user uninstall B and software E.
If step 51 user selects unloading, then software administration service unit 101 is uninstall E and software B, the uninstall process of its process such as software A.
If step 52 user selects not unload, then can not uninstall B, withdraw from uninstall process.
The above only is preferred embodiment of the present invention, not in order to restriction the present invention, all any modifications of being made within the spirit and principles in the present invention, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.
Claims (7)
1. the method for a management software installation/unloading, it is characterized in that, software dependency information description document is set, and described file comprises: the component software and the version of the required dependence of normal operation of the software of the required dependence of normal operation of software and version, software, and this method also comprises:
When install software, user side judges whether to exist the software of wanting install software to rely on according to the software dependency information description document that is provided with, if exist, user side is installed the software that is relied on earlier, installs and wants install software; Otherwise user side is installed and is wanted install software; Described user side is installed the software process that is relied on earlier: the user side setting provides the software administration service unit of pre-mounting interface, the software installation unit that is used for the storing software installation procedure calls the pre-mounting interface of software administration service unit, is obtained by the installation procedure of depended software by the software administration service unit and also installs by depended software; Perhaps want the installation procedure of install software to obtain, install by depended software by the installation procedure of depended software by user side;
When uninstall, user side judges whether to exist according to the software dependency information description document that is provided with and depends on the software of wanting uninstall, if exist, user side not uninstall or the user side software that will unload and the software that depends on institute's uninstall all unloads; Otherwise, the software that the user side unloading will unload;
The dependency information description document of wanting uninstall and depending on the software correspondence of institute's uninstall that user side will be arranged in the local software information bank is deleted.
2. the method for claim 1 is characterized in that, described software dependency information description document is a user side during the dependency information description document of install software, and this document is stored in the local software information bank that user side is provided with.
3. the method for claim 1 is characterized in that, described software dependency information description document is a user side not during the dependency information description document of install software, and this document is stored in to be provided in the software of the software installation procedure installation unit.
4. the method for claim 1 is characterized in that, after described user side was installed by depended software earlier, this method further comprised:
User side will be kept in the local software information bank of setting by the dependency information description document of depended software, and be labeled as passive installation;
After install software was wanted in described installation, this method further comprised: user side is kept at the dependency information description document of software in the local software information bank of setting, and is labeled as initiatively installation.
5. the method for claim 1 is characterized in that, this method further comprises:
User side judge want uninstall with depend on institute's uninstall whether software relied on be labeled as passive installed software and also relied on by mounted other software of user side, if there is no depend on other software of this passive install software, user side unloads this and is labeled as passive installed software, and the dependency information description document that will be arranged on this passive install software in the local software information bank is deleted; Otherwise user side does not process, and finishes.
6. the method for claim 1 is characterized in that, described software is the software with one or more assemblies.
7. method as claimed in claim 6 is characterized in that, when software was made amendment, this method further comprised:
Software increases assembly, user side judges according to the software dependency information description document that assembly is set whether user side has installed software and the assembly of wanting installation component to rely on, if do not install, user side is installed software and the assembly that is relied on earlier, installs and wants installation component; Otherwise user side is installed and is wanted installation component;
When the unloading assembly, user side is judged according to the software dependency information description document that assembly is set whether user side exists and is depended on the software and the assembly that will unload assembly, if exist, user side does not unload will unload the assembly that assembly or user side will unload and depend on the software and the assembly that will unload assembly and all unloads; Otherwise, the assembly that the user side unloading will unload.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100554997A CN100399267C (en) | 2005-03-18 | 2005-03-18 | Method of managing software installation and unloading |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100554997A CN100399267C (en) | 2005-03-18 | 2005-03-18 | Method of managing software installation and unloading |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1834913A CN1834913A (en) | 2006-09-20 |
| CN100399267C true CN100399267C (en) | 2008-07-02 |
Family
ID=37002678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100554997A Expired - Fee Related CN100399267C (en) | 2005-03-18 | 2005-03-18 | Method of managing software installation and unloading |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100399267C (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012065464A1 (en) * | 2010-11-18 | 2012-05-24 | 中兴通讯股份有限公司 | Software installation method and device |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100501673C (en) * | 2006-12-31 | 2009-06-17 | 成都迈普产业集团有限公司 | Method for installing software installation packet |
| JP5293344B2 (en) * | 2009-03-30 | 2013-09-18 | 株式会社リコー | Image processing apparatus, software distribution system, installation processing method, and program |
| CN102073582A (en) * | 2010-07-30 | 2011-05-25 | 兰雨晴 | Conflict-based method for checking dependency of software package |
| CN102043655B (en) * | 2011-01-04 | 2015-03-25 | 奇智软件（北京）有限公司 | Method and system for carrying out advanced uninstall on software |
| JP5790222B2 (en) * | 2011-07-12 | 2015-10-07 | 株式会社リコー | Communication device, update method, and update program |
| CN105159710A (en) * | 2012-03-31 | 2015-12-16 | 北京奇虎科技有限公司 | Software uninstalling method and apparatus |
| CN103425512B (en) * | 2013-08-19 | 2016-12-28 | 曙光信息产业股份有限公司 | A kind of software package management method and system |
| CN106648719A (en) * | 2015-11-02 | 2017-05-10 | 天脉聚源（北京）科技有限公司 | Method and system for updating server codes |
| CN105677399A (en) * | 2015-12-30 | 2016-06-15 | 广东欧珀移动通信有限公司 | Application deleting method and application deleting device |
| CN106250185A (en) * | 2016-07-29 | 2016-12-21 | 宇龙计算机通信科技(深圳)有限公司 | The control method of application program, control device and terminal |
| CN111158719B (en) * | 2019-12-26 | 2023-06-16 | 湖南快乐阳光互动娱乐传媒有限公司 | Application software upgrading method and device |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040255291A1 (en) * | 2003-01-17 | 2004-12-16 | Sierer Brian H. | Installing software using programmatic component dependency analysis |
-
2005
- 2005-03-18 CN CNB2005100554997A patent/CN100399267C/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040255291A1 (en) * | 2003-01-17 | 2004-12-16 | Sierer Brian H. | Installing software using programmatic component dependency analysis |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012065464A1 (en) * | 2010-11-18 | 2012-05-24 | 中兴通讯股份有限公司 | Software installation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1834913A (en) | 2006-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100399267C (en) | Method of managing software installation and unloading | |
| EP1224543B1 (en) | Fixing applications that are incompatible to the operating system by providing stubs for apis | |
| CN100426235C (en) | System and method for representing user process to software package in software package management system | |
| US8245216B2 (en) | Patch management system | |
| US8112745B2 (en) | Apparatus and method for capabilities verification and restriction of managed applications in an execution environment | |
| CN109614167B (en) | Method and system for managing plug-ins | |
| US20060230398A1 (en) | Install processing apparatus, processing method, storage medium, and program | |
| US20160378458A1 (en) | Method and device for system application installation package, and terminal | |
| CN102736978A (en) | Method and device for detecting installation status of application program | |
| JP2003256225A (en) | Computer system, failure countermeasure and program for making computer system function | |
| US20100017503A1 (en) | Download server and method for installing and updating application program using partitioning of shared library | |
| CN108228077B (en) | Storage area management method, operation method, device, equipment and readable medium | |
| CN103345411A (en) | Method and device for uninstalling application program | |
| US7216344B2 (en) | Side-by-side drivers | |
| CN111857765A (en) | Plug-in system for drug design system, and generation method and updating method thereof | |
| CN102999352A (en) | Embedded system assembly loading method | |
| CN104731622A (en) | Application program loading method and device and mobile terminal | |
| CN104932887A (en) | Plug-in management method of platform system and platform system | |
| CN101877655A (en) | Network management system, network management server and method | |
| US6336215B1 (en) | Apparatus and method for on-line code only replacement of a running program using checkpoints | |
| US8250558B2 (en) | Dynamic linked library add-on features | |
| CN116679971A (en) | Thermal repair method, device, electronic equipment and storage medium | |
| CN115994003A (en) | Processing method and processing device for shared object in operating system | |
| CN116150121A (en) | Network attached storage replacement method and related device | |
| CN111209197B (en) | Application continuous integration test method, system, equipment and storage medium |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080702 Termination date: 20210318 |