CN116932029A - Component library management method and device, intelligent equipment and storage medium - Google Patents
Component library management method and device, intelligent equipment and storage medium Download PDFInfo
- Publication number
- CN116932029A CN116932029A CN202210369390.4A CN202210369390A CN116932029A CN 116932029 A CN116932029 A CN 116932029A CN 202210369390 A CN202210369390 A CN 202210369390A CN 116932029 A CN116932029 A CN 116932029A
- Authority
- CN
- China
- Prior art keywords
- target
- component
- identification information
- package
- configuration file
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 114
- 230000001419 dependent effect Effects 0.000 claims abstract description 145
- 238000000034 method Methods 0.000 claims description 24
- 230000015654 memory Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 10
- 230000006870 function Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012544 monitoring process 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/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application discloses a component library management method, a device, intelligent equipment and a storage medium, wherein when a management instruction for a component in a component library is received, a target component corresponding to the management instruction is acquired, and a target dependency package corresponding to the target component is acquired; acquiring a component configuration file and acquiring target identification information of the target dependent package; and managing the target component and the target dependent package according to the component configuration file and the target identification information. The problem of lower management efficiency of the component library is solved, and the management efficiency of the component library is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and apparatus for managing a component library, an intelligent device, and a storage medium.
Background
Based on component library development management and daily warehouse management, each component or project is managed by using one warehouse separately, if multiple components exist in the project of the component library and have a dependency relationship, we generally need to issue the whole project package for management, the version number needs to be manually modified when issuing, other components in the same project can be issued when one component is modified, so that the volume of a bag body is very large, and when multiple components exist in the project, one component in the project cannot be managed separately, so that the component management efficiency in the component library is low.
Disclosure of Invention
The embodiment of the application provides a component library management method, a device, intelligent equipment and a storage medium, which can improve the management efficiency of a component library.
In order to solve the technical problems, the embodiment of the application provides the following technical scheme:
the embodiment of the application provides a component library management method, which comprises the following steps:
when a management instruction aiming at a component in a component library is received, acquiring a target component corresponding to the management instruction and acquiring a target dependency package corresponding to the target component;
acquiring a component configuration file and acquiring target identification information of the target dependent package;
and managing the target component and the target dependent package according to the component configuration file and the target identification information.
In an embodiment, the component profile includes a first profile and a second profile, and the obtaining the component profile includes:
acquiring a first configuration file corresponding to the component library and a second configuration file corresponding to the target component;
the managing the target component and the target dependency package according to the component configuration file and the target identification information includes:
managing the target component and the target dependency package according to the first configuration file, the second configuration file and the target identification information; or alternatively, the process may be performed,
and managing the target component and the target dependent package according to the target identification information and the first configuration file or the second configuration file.
In an embodiment, the managing the target component and the target dependency package according to the component configuration file and the target identification information includes:
acquiring identification information corresponding to the dependent packages in a public dependent package set, wherein the dependent packages in the public dependent package set are the dependent packages shared by the components in the component library;
judging whether the target identification information is matched with the identification information or not;
and if the target identification information is matched with the identification information, managing the target component and the target dependent package according to the first configuration file.
In one embodiment, the determining whether the target identification information matches the identification information includes
And if the target identification information is not matched with the identification information, managing the target component and the target dependent package according to the second configuration file.
In an embodiment, the managing the target component and the target dependency package according to the component configuration file and the target identification information further includes:
judging the number of the target dependent packets;
and if the number of the target dependent packages is multiple, and a plurality of target dependent packages have a first target dependent package with the target identification information matched with the identification information corresponding to the dependent package in the public dependent package set and a second target dependent package with the target identification information not matched with the identification information corresponding to the dependent package in the public dependent package set, managing the first target dependent package according to the first configuration file and managing the second target dependent package according to the second configuration file.
In an embodiment, the obtaining the target dependency package corresponding to the target component includes:
judging whether the target component has a dependent package or not;
and if the target component has the dependent package, acquiring the target dependent package corresponding to the target component.
In one embodiment, after the determining whether the target component has a dependency package, the method further includes:
and if the target component has no dependency package, managing the target component according to the second configuration file.
In one embodiment, after the determining whether the target component has a dependency package, the method further includes:
judging whether the target component has a dependency relationship with other components;
if the target component has no dependency package and the target component has a dependency relationship with other components, managing the target component according to the first configuration file, and synchronously updating the components with the dependency relationship with the target component;
and if the target component has no dependency package and has no dependency relationship with other components, managing the target component according to the second configuration file.
In one embodiment, the method further comprises:
if the target component has a dependent package and the target component has no dependency relationship with other components, acquiring a target dependent package corresponding to the target component and acquiring target identification information of the target dependent package;
and managing the target component and the target dependent package according to the component configuration file and the target identification information.
In one embodiment, the method further comprises:
if the target component has a dependency package and the target component has a dependency relationship with other components, acquiring a target dependency package corresponding to the target component and acquiring target identification information of the target dependency package;
and managing the target component and the target dependency package according to the component configuration file and the target identification information, and synchronously updating the components with the dependency relationship with the target component.
According to an aspect of the present application, there is also provided a component library management apparatus including:
the first acquisition module is used for acquiring a target component corresponding to a management instruction when receiving the management instruction aiming at the component in the component library and acquiring a target dependency package corresponding to the target component;
the second acquisition module is used for acquiring a component configuration file and acquiring target identification information of the target dependent package;
and the management module is used for managing the target component and the target dependent package according to the component configuration file and the target identification information.
According to an aspect of the present application, there is also provided an intelligent device, including a processor and a memory, where the memory stores a computer program, and when the processor invokes the computer program in the memory, any one of the component library management methods provided by the embodiments of the present application is executed.
According to an aspect of the present application, there is also provided a storage medium for storing a computer program loaded by a processor to perform any of the component library management methods provided by the embodiments of the present application.
In the embodiment of the application, when receiving the management instruction for the components in the component library, the component library management device can acquire the target component corresponding to the management instruction and acquire the target dependency package corresponding to the target component; acquiring a component configuration file and acquiring target identification information of the target dependent package; and managing the target component and the target dependent package according to the component configuration file and the target identification information. Therefore, according to the component configuration file and the identification information of the target dependency package corresponding to the target component, the target component and the target dependency package can be uniformly managed, the common dependency package of the repeated management component is avoided, and the independent dependency package of the target component can be independently managed, so that the management efficiency of the component library is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a component library management method according to an embodiment of the present application;
FIG. 2 is another flow chart of a component library management method according to an embodiment of the present application;
FIG. 3 is another flow chart of a component library management method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a component library management apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an intelligent device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to fall within the scope of the application.
The embodiment of the application provides a component library management method, a device, intelligent equipment and a storage medium (namely a computer readable storage medium). The component library management method may be applied to a component library management device, which may be specifically integrated in an intelligent device, where the intelligent device may be in communication connection with a server, and the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server that provides a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a content distribution network (Content Delivery Network, CDN), and a basic cloud computing service such as a big data and an artificial intelligent platform, but is not limited thereto.
The following will describe in detail. The following description of the embodiments is not intended to limit the preferred embodiments.
In this embodiment, description will be made from the perspective of an intelligent device, referring to fig. 1, fig. 1 is a flow chart of a component library management method according to an embodiment of the present application. The component library management method may include:
s10, when a management instruction for a component in the component library is received, acquiring a target component corresponding to the management instruction and acquiring a target dependency package corresponding to the target component.
The components may be data packets, and the items in the component library may include a plurality of components or may be one component. If there are multiple components, there may or may not be a dependency relationship between different components. The components can have dependency packages or no dependency packages, the dependency packages can be unique to the components or common to a plurality of components in a component library, wherein the dependency packages unique to the components can be placed in a dependency package set unique to the components and can be obtained according to configuration files corresponding to the components, and the dependency packages common to the components can be placed in a common dependency package set and can be obtained according to unified configuration files corresponding to the component library.
The management instruction may include a component modification instruction, a component issue instruction, a component packaging instruction, a component download instruction, a component installation instruction, a component upgrade instruction, and the like, and the management instruction may include identification information of a target component to be managed, so that the component library management device may acquire the target component according to the identification information in the management instruction, and the management instruction may be sent to the component library management device by a user. When receiving the management instruction, the component library management device may acquire a target component corresponding to the management instruction from a local resource of the component library management device, or may acquire the target component from a server or other devices connected to the component library management device according to the management instruction. The target dependency package may be in a common dependency package set or in a dependency package set unique to the target component.
S20, acquiring a component configuration file and acquiring target identification information of a target dependent package.
Optionally, in an embodiment, the component configuration file may include a first configuration file and a second configuration file, and acquiring the component configuration file may include: the method comprises the steps of obtaining a first configuration file corresponding to a component library and obtaining a second configuration file corresponding to a target component.
The configuration file may be a package. Json file, and the configuration file may include target identification information of a target dependency package, for example, a package name or version number of the dependency package, etc., so as to manage the target dependency package according to the configuration file when receiving the management instruction. For example, a unified management tool, such as a yarn command, may be used to install or upgrade all shared dependency packages, while for each component a separate dependency package may be installed or upgraded via the package json configuration file corresponding to the target component.
It should be noted that, in an embodiment, when a developer performs development management on a component library, a component library is created, and a unified component entry is created for the component library to uniformly manage a plurality of items or components, after that, lerna may be installed to optimize and use git and npm to manage a workflow of managing and storing a plurality of packages, and use a yarn command to manage a dependency package of a component or a dependency relationship between components, then use a rollup configuration to uniformly package a file entry, each component may use this as a package dependency, so as to manage, for example, package compression on the component, then create the component and complete logic writing of the component, optionally, a uniform package tool may be selected to package the component, then release the item obtained by packaging the component, specifically, may log npm, operate lerna publish, may simultaneously submit the item to git, and release all modified and newly added components.
S30, managing the target component and the target dependent package according to the component configuration file and the target identification information.
Correspondingly, managing the target component and the target dependency package according to the component configuration file and the target identification information may include: managing a target component and a target dependent package according to the first configuration file, the second configuration file and the target identification information; or, managing the target component and the target dependency package according to the target identification information and the first configuration file or the second configuration file.
Optionally, in an embodiment, in S10, obtaining a target dependency package corresponding to the target component includes: judging whether the target component has a dependent package or not;
the dependency package may refer to a third party program or function used instead of a component written in the component library, and whether the dependency package exists in the target component may be determined according to the second configuration file.
And if the target component has the dependent package, acquiring the target dependent package corresponding to the target component. For example, if it is determined that the target component has a dependency package, a target dependency package corresponding to the target component is obtained, target identification information of the target dependency package is obtained, and then the target component and the target dependency package are managed according to the component configuration file and the target identification information.
And if the target component has no dependency package, managing the target component according to the second configuration file.
In the technical scheme provided by the embodiment, when receiving the management instruction for the components in the component library, the component library management device can acquire a target component corresponding to the management instruction and acquire a target dependency package corresponding to the target component; acquiring a component configuration file and acquiring target identification information of a target dependent package; and managing the target component and the target dependent package according to the component configuration file and the target identification information. Therefore, according to the component configuration file and the identification information of the target dependency package corresponding to the target component, the target component and the target dependency package can be uniformly managed, the common dependency package of the repeated management component is avoided, and the independent dependency package of the target component can be independently managed, so that the management efficiency of the component library is improved.
Based on the above embodiments, referring to fig. 2, fig. 2 is another flow chart of the component library management method provided by the embodiment of the present application, S30 may include:
s31, acquiring identification information corresponding to the dependent packages in the public dependent package set, wherein the dependent packages in the public dependent package set are the dependent packages shared by the components in the component library.
It will be appreciated that in this embodiment, if there are shared dependent packages for multiple components in the component library, for example, if component a, component B and component C all depend on the dependent package X, the dependent package X is placed in a common dependent package set, and if component a and component B depend on the dependent package O, component B and component C depend on the dependent package P, the dependent package O and the dependent package P are both placed in the common dependent package set.
S32, judging whether the target identification information is matched with the identification information.
Optionally, if the target identification information of the target dependency package is the same as the identification information corresponding to the dependency package in the public dependency package set, it is determined that the target identification information is matched with the identification information, that is, the target dependency package is the public dependency package, and unified management is required to be performed on the target dependency package according to the first configuration file corresponding to the component library. If the target identification information of the target dependent package is different from the identification information corresponding to the dependent package in the public dependent package set, the target identification information is not matched with the identification information, that is, the target dependent package is a unique dependent package of the target component, and at the moment, the target dependent package is managed according to the second configuration file corresponding to the target component.
And S33, if the target identification information is matched with the identification information, managing the target component and the target dependent package according to the first configuration file.
If the target identification information is matched with the identification information, that is, the target dependent package is a public dependent package, in an embodiment, if the target components are multiple, the target identification information of the target dependent package corresponding to the multiple target components is obtained; matching the plurality of target identification information; if the plurality of target identification information is matched, the plurality of target components and the target dependent packages corresponding to the plurality of target components are managed according to the first configuration information,
for example, when a component downloading instruction is received, a target component corresponding to the downloading instruction and a target dependency package corresponding to the target component are obtained, if the target identification information corresponding to the target dependency package X corresponding to the target component a and the target dependency package Y corresponding to the target component B are the same, that is, the target dependency package X and the target dependency package Y are the same and are common dependency packages, the target dependency package is downloaded only once according to the first configuration information, and is not required to be downloaded twice, so that the component library management efficiency is improved.
Optionally, after S32, the method may further include: and if the target identification information is not matched with the identification information, managing the target component and the target dependent package according to the second configuration file.
For example, when a modification instruction of a target component is received, if target identification information of a target dependency package corresponding to the target component is different from identification information corresponding to a dependency package in a common dependency package set, it is determined that the target identification information is not matched with the identification information, that is, the target dependency package is a dependency package unique to the target component, and at this time, the target component and the target dependency package can be modified only according to a second configuration file corresponding to the target component, without modifying other components in the component library together, thereby improving management efficiency of the component library.
Optionally, based on the above embodiment, S30 may further include:
judging the number of target dependent packets; if the number of the target dependent packets is multiple, and the target dependent packets have a first target dependent packet with target identification information matched with the identification information corresponding to the dependent packets in the public dependent packet set and a second target dependent packet with target identification information not matched with the identification information corresponding to the dependent packets in the public dependent packet set, the first target dependent packet is managed according to the first configuration file, and the second target dependent packet is managed according to the second configuration file.
For example, the target component a has a target dependency package X and a target dependency package Y, where the target dependency package X is a common dependency package and needs to be comprehensively managed according to the first configuration file, and the target dependency package Y is a dependency package unique to the target component a and only needs to be managed through the second configuration file.
In the technical scheme provided by the embodiment of the application, a component library management device acquires identification information corresponding to a dependent package in a public dependent package set, wherein the dependent package in the public dependent package set is a dependent package shared by components in a component library; judging whether the target identification information is matched with the identification information; and if the target identification information is matched with the identification information, managing the target component and the target dependent package according to the first configuration file. Therefore, the target dependency package is divided into the public dependency package and the unique dependency package of the target component, so that the target dependency package can be comprehensively managed through the first configuration file corresponding to the component library when the target dependency package is the public dependency package, the effect of repeatedly managing the target dependency package is achieved, and the target dependency package can be independently managed through the second configuration file unique to the target component when the target dependency package is the unique dependency package without affecting other components, and the management efficiency of the component library is improved.
Referring to fig. 3, fig. 3 is another flow chart of a component library management method according to an embodiment of the present application, after determining whether a target component has a dependency package, the method further includes:
s40, judging whether the target component and other components have a dependency relationship.
The target component has a dependency relationship with other components in the component library, which may mean that a reference relationship exists between the target component a and the component B in the component library, or that a parent-child component relationship exists.
S50, if the target component has no dependency package and the target component has a dependency relationship with other components, the target component is managed according to the first configuration file, and the components having the dependency relationship with the target component are synchronously updated.
For example, if a version number modification instruction for the target component a is received, the target component a has no dependency package, and the target component a has a dependency relationship with the component B in the component library, the version number of the target component a is modified according to the first configuration file, and the version number of the target component a in the component B is synchronously updated.
S60, if the target component has no dependency package and the target component has no dependency relationship with other components, the target component is managed according to the second configuration file.
Optionally, in an embodiment, the component library management method further includes: if the target component has a dependent package and the target component has no dependency relationship with other components, acquiring a target dependent package corresponding to the target component and acquiring target identification information of the target dependent package; and managing the target component and the target dependent package according to the component configuration file and the target identification information.
For example, acquiring identification information corresponding to the dependent package in the public dependent package set; judging whether the target identification information is matched with the identification information; if the target identification information is matched with the identification information, managing the target component and the target dependent package according to the first configuration file; and if the target identification information is not matched with the identification information, managing the target component and the target dependent package according to the second configuration file.
Optionally, in an embodiment, the component library management method further includes: if the target component has a dependency package and the target component has a dependency relationship with other components, acquiring a target dependency package corresponding to the target component and acquiring target identification information of the target dependency package;
and managing the target component and the target dependency package according to the component configuration file and the target identification information, and synchronously updating the components with the dependency relationship with the target component.
For example, acquiring identification information corresponding to the dependent package in the public dependent package set; judging whether the target identification information is matched with the identification information; if the target identification information is matched with the identification information, managing a target component and a target dependency package according to the first configuration file, and synchronously updating contents related to the target component in the component with the dependency relationship with the target component; if the target identification information is not matched with the identification information, the target component and the target dependency package are managed according to the second configuration file, and the content related to the target component in the component with the dependency relationship with the target component is synchronously updated.
In the technical scheme provided by the embodiment of the application, whether the target component and other components have a dependency relationship is judged; if the target component has no dependency package and the target component has a dependency relationship with other components, managing the target component according to the first configuration file, and synchronously updating the components having the dependency relationship with the target component; and if the target component has no dependency package and the target component has no dependency relationship with other components, managing the target component according to the second configuration file. When the target component is managed, other components with the dependency relationship can be synchronously updated through the first configuration file of the component library, and the other components with the dependency relationship are not required to be manually managed again, so that the component library management efficiency is improved.
In order to facilitate better implementation of the component library management method provided by the embodiment of the application, the embodiment of the application also provides a device based on the component library management method. Where the meaning of nouns is the same as in the component library management method described above, specific implementation details may be referred to in the description of the method embodiments.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a component library management device according to an embodiment of the present application, where the component library management device 300 may include a first obtaining module 301, a second obtaining module 302, a management module 303, and so on.
The first obtaining module 301 is configured to obtain, when receiving a management instruction for a component in the component library, a target component corresponding to the management instruction, and obtain a target dependency package corresponding to the target component;
a second obtaining module 302, configured to obtain a component configuration file, and obtain target identification information of a target dependency package;
and the management module 303 is used for managing the target component and the target dependency package according to the component configuration file and the target identification information.
Optionally, the component library management apparatus may further include:
the third acquisition module is used for acquiring a first configuration file corresponding to the component library and a second configuration file corresponding to the target component;
the first management module is used for managing the target component and the target dependent package according to the first configuration file, the second configuration file and the target identification information; or alternatively, the process may be performed,
and the second management module is used for managing the target component and the target dependent package according to the target identification information and the first configuration file or the second configuration file.
A fourth obtaining module, configured to obtain identification information corresponding to a dependency package in a common dependency package set, where the dependency package in the common dependency package set is a dependency package shared by components in the component library;
the first judging module is used for judging whether the target identification information is matched with the identification information;
and the third management module is used for managing the target component and the target dependent package according to the first configuration file if the target identification information is matched with the identification information.
And the fourth management module is used for managing the target component and the target dependent package according to the second configuration file if the target identification information is not matched with the identification information.
The second judging module is used for judging the number of the target dependent packets;
and the fifth management module is used for managing the first target dependent package according to the first configuration file and managing the second target dependent package according to the second configuration file if the number of the target dependent packages is multiple, and the target dependent packages in the multiple target dependent packages have a first target dependent package with target identification information matched with the identification information corresponding to the dependent packages in the public dependent package set and a second target dependent package with target identification information not matched with the identification information corresponding to the dependent packages in the public dependent package set.
The third judging module is used for judging whether the target component has a dependent package or not;
and the fifth acquisition module is used for acquiring the target dependency package corresponding to the target component if the target component has the dependency package.
And the sixth management module is used for managing the target component according to the second configuration file if the target component has no dependency package.
The fourth judging module is used for judging whether the target component and other components have a dependency relationship or not;
the first updating module is used for managing the target component according to the first configuration file and synchronously updating the component with the dependency relationship with the target component if the target component has no dependency package and the target component has the dependency relationship with other components;
and the seventh management module is used for managing the target component according to the second configuration file if the target component has no dependency package and the target component has no dependency relationship with other components.
A seventh obtaining module, configured to obtain, if the target component has a dependency package and the target component has no dependency relationship with other components, a target dependency package corresponding to the target component, and obtain target identification information of the target dependency package;
and the eighth management module is used for managing the target component and the target dependent package according to the component configuration file and the target identification information.
An eighth obtaining module, configured to obtain a target dependency package corresponding to the target component and obtain target identification information of the target dependency package if the target component has a dependency package and the target component has a dependency relationship with other components;
and the second updating module is used for managing the target component and the target dependency package according to the component configuration file and the target identification information and synchronously updating the component with the dependency relationship with the target component.
The embodiment of the application also provides an intelligent device, which can be a mobile phone, a computer, an intelligent screen and other terminals, as shown in fig. 5, and shows a schematic structural diagram of the intelligent device according to the embodiment of the application, specifically:
the smart device may include one or more processors 401 of a processing core, one or more memories 402 of a computer readable storage medium, a power supply 403, and an input unit 404. Those skilled in the art will appreciate that the smart device architecture shown in fig. 5 is not limiting of the smart device and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. Wherein:
the processor 401 is a control center of the smart device, connects various parts of the entire smart device using various interfaces and lines, and performs various functions of the smart device and processes data by running or executing software programs and/or modules stored in the memory 402, and calling data stored in the memory 402, thereby performing overall monitoring of the smart device. Optionally, processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application program, etc., and the modem processor mainly processes wireless communication. It will be appreciated that the modem processor described above may not be integrated into the processor 401.
The memory 402 may be used to store software programs and modules, and the processor 401 executes various functional applications and data processing by executing the software programs and modules stored in the memory 402. The memory 402 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like; the storage data area may store data created according to the use of the smart device, etc. In addition, memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.
The smart device also includes a power supply 403 for powering the various components, preferably, the power supply 403 is logically connected to the processor 401 by a power management system, so that functions such as charging, discharging, and power consumption management can be performed by the power management system. The power supply 403 may also include one or more of any of a direct current or alternating current power supply, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
The smart device may also include an input unit 404, which input unit 404 may be used to receive entered numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Although not shown, the smart device may further include a display unit or the like, which is not described herein. In this embodiment, the processor 401 in the smart device loads executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 executes the application programs stored in the memory 402, so as to implement various functions as follows:
when a management instruction for a component in a component library is received, acquiring a target component corresponding to the management instruction and acquiring a target dependency package corresponding to the target component; acquiring a component configuration file and acquiring target identification information of a target dependent package; and managing the target component and the target dependent package according to the component configuration file and the target identification information.
In the foregoing embodiments, the descriptions of the embodiments are focused on, and for those portions of an embodiment that are not described in detail, reference may be made to the foregoing detailed description of the component library management method, which is not repeated herein.
According to one aspect of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the smart device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the smart device performs the methods provided in the various alternative implementations of the above embodiments.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by computer instructions, or by controlling associated hardware, that may be stored in a storage medium and loaded and executed by a processor, where the storage medium is a computer-readable storage medium. To this end, an embodiment of the present application provides a storage medium in which a computer program is stored, where the computer program may include computer instructions that can be loaded by a processor to perform any of the component library management methods provided by the embodiments of the present application.
The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.
Wherein the storage medium may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.
Because the computer instructions stored in the storage medium can execute any component library management method provided by the embodiment of the present application, the beneficial effects that any component library management method provided by the embodiment of the present application can achieve can be achieved, and detailed descriptions are omitted herein.
The above describes in detail a component library management method, device, intelligent device and storage medium provided by the embodiments of the present application, and specific examples are applied to describe the principles and implementations of the present application, where the description of the above embodiments is only used to help understand the method and core idea of the present application; meanwhile, as those skilled in the art will vary in the specific embodiments and application scope according to the ideas of the present application, the present description should not be construed as limiting the present application in summary.
Claims (13)
1. A method of component library management, the method comprising:
when a management instruction aiming at a component in a component library is received, acquiring a target component corresponding to the management instruction and acquiring a target dependency package corresponding to the target component;
acquiring a component configuration file and acquiring target identification information of the target dependent package;
and managing the target component and the target dependent package according to the component configuration file and the target identification information.
2. The component library management method of claim 1, wherein the component configuration file comprises a first configuration file and a second configuration file, and the obtaining the component configuration file comprises:
acquiring a first configuration file corresponding to the component library and a second configuration file corresponding to the target component;
the managing the target component and the target dependency package according to the component configuration file and the target identification information includes:
managing the target component and the target dependency package according to the first configuration file, the second configuration file and the target identification information; or alternatively, the process may be performed,
and managing the target component and the target dependent package according to the target identification information and the first configuration file or the second configuration file.
3. The component library management method according to any one of claims 1-2, wherein the managing the target component and the target dependency package according to the component profile and the target identification information comprises:
acquiring identification information corresponding to the dependent packages in a public dependent package set, wherein the dependent packages in the public dependent package set are the dependent packages shared by the components in the component library;
judging whether the target identification information is matched with the identification information or not;
and if the target identification information is matched with the identification information, managing the target component and the target dependent package according to the first configuration file.
4. The component library management method according to claim 3, wherein after said determining whether the target identification information matches the identification information, comprising:
and if the target identification information is not matched with the identification information, managing the target component and the target dependent package according to the second configuration file.
5. The component library management method according to claim 3, wherein said managing said target component and said target dependency package according to said component profile and said target identification information, further comprises:
judging the number of the target dependent packets;
and if the number of the target dependent packages is multiple, and a plurality of target dependent packages have a first target dependent package with the target identification information matched with the identification information corresponding to the dependent package in the public dependent package set and a second target dependent package with the target identification information not matched with the identification information corresponding to the dependent package in the public dependent package set, managing the first target dependent package according to the first configuration file and managing the second target dependent package according to the second configuration file.
6. The component library management method according to claim 1, wherein the obtaining the target dependency package corresponding to the target component includes:
judging whether the target component has a dependent package or not;
and if the target component has the dependent package, acquiring the target dependent package corresponding to the target component.
7. The component library management method of claim 6, wherein after said determining whether the target component has a dependency package, the method further comprises:
and if the target component has no dependency package, managing the target component according to the second configuration file.
8. The component library management method of claim 7, wherein after said determining whether the target component has a dependency package, the method further comprises:
judging whether the target component has a dependency relationship with other components;
if the target component has no dependency package and the target component has a dependency relationship with other components, managing the target component according to the first configuration file, and synchronously updating the components with the dependency relationship with the target component;
and if the target component has no dependency package and has no dependency relationship with other components, managing the target component according to the second configuration file.
9. The component library management method according to any one of claims 1 to 8, further comprising:
if the target component has a dependent package and the target component has no dependency relationship with other components, acquiring a target dependent package corresponding to the target component and acquiring target identification information of the target dependent package;
and managing the target component and the target dependent package according to the component configuration file and the target identification information.
10. The component library management method of claim 9, wherein the method further comprises:
if the target component has a dependency package and the target component has a dependency relationship with other components, acquiring a target dependency package corresponding to the target component and acquiring target identification information of the target dependency package;
and managing the target component and the target dependency package according to the component configuration file and the target identification information, and synchronously updating the components with the dependency relationship with the target component.
11. A component library management apparatus, comprising:
the first acquisition module is used for acquiring a target component corresponding to a management instruction when receiving the management instruction aiming at the component in the component library and acquiring a target dependency package corresponding to the target component;
the second acquisition module is used for acquiring a component configuration file and acquiring target identification information of the target dependent package;
and the management module is used for managing the target component and the target dependent package according to the component configuration file and the target identification information.
12. A smart device comprising a processor and a memory, wherein the memory has a computer program stored therein, and wherein the processor executes the component library management method of any one of claims 1 to 10 when calling the computer program in the memory.
13. A storage medium storing a computer program loaded by a processor to perform the component library management method of any one of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210369390.4A CN116932029A (en) | 2022-04-08 | 2022-04-08 | Component library management method and device, intelligent equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210369390.4A CN116932029A (en) | 2022-04-08 | 2022-04-08 | Component library management method and device, intelligent equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116932029A true CN116932029A (en) | 2023-10-24 |
Family
ID=88393058
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210369390.4A Pending CN116932029A (en) | 2022-04-08 | 2022-04-08 | Component library management method and device, intelligent equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116932029A (en) |
-
2022
- 2022-04-08 CN CN202210369390.4A patent/CN116932029A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100511156C (en) | Apparatus for compulsively terminating thread blocked on input/output operation and method for the same | |
| US10949216B2 (en) | Support for third-party kernel modules on host operating systems | |
| CN110569250B (en) | Management method and device for analysis library of Internet of things network element | |
| US20150100968A1 (en) | Operating Programs on a Computer Cluster | |
| CN110888658B (en) | Method and device for dynamically changing function modules in application program and storage medium | |
| CN112507263B (en) | Page loading updating method and device, electronic equipment and storage medium | |
| CN109885332A (en) | Image quality chip software upgrade method, device, display equipment and storage medium | |
| CN114327484A (en) | Multi-architecture supporting K8S integration and deployment method, system and storage medium | |
| CN113590304A (en) | Business data processing method and device, computer equipment and storage medium | |
| CN111090442A (en) | Application updating method and device and storage medium | |
| CN116932029A (en) | Component library management method and device, intelligent equipment and storage medium | |
| CN113791809B (en) | Application exception handling method and device and computer readable storage medium | |
| CN112667491B (en) | Function test method and device for virtual machine | |
| WO2021129853A1 (en) | Mobile service upgrade method and apparatus, and terminal | |
| CN114756362A (en) | Resource quota management method and system, intelligent terminal and storage medium | |
| CN115964061A (en) | Plug-in updating method and device, electronic equipment and computer readable storage medium | |
| CN114327709A (en) | Control page generation method and device, intelligent device and storage medium | |
| CN116954678A (en) | Object updating method, device and computer readable storage medium | |
| CN116521307A (en) | Cluster management method, electronic device and storage medium | |
| CN116302710A (en) | Application version rollback method, device, computer equipment and storage medium | |
| CN115495215A (en) | GPU (graphics processing Unit) sharing method, device, equipment and medium | |
| CN117407270A (en) | Performance test method, device, equipment to be tested and computer storage medium | |
| CN117407279A (en) | Software component map generation method and related equipment thereof | |
| CN116931914A (en) | Page rendering method, page rendering device, electronic device and computer readable storage medium | |
| CN117170698A (en) | Firmware upgrading method, device, electronic equipment and computer readable 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 |