JP2023159710A - Information processing device, installation method, and program - Google Patents

Abstract

To eliminate a failure that occurs when a library is called by an application with a different authority due to fixation of operation of the library by the authority of an application that was called during initialization.SOLUTION: A method of installing an application by an information processing device, includes: determining whether or not an application being installed is calling a specific library; installing the application if the specific library is being called, further copying the specific library to a location dependent on the application, and installing the same; and making settings so that the application preferentially calls the specific library from the installed location.SELECTED DRAWING: Figure 1A

Description

The present invention relates to an information processing device, an installation method, and a program that enable an embedded system to install and execute an application for expansion.

Conventionally, there are the following application platforms that allow one or more applications to be installed and executed. That is, the installation medium includes the libraries necessary for executing the application to be installed. If the second library, which has the same calling convention as the library located on the installed system, is a version that is incompatible with the application, perform the following processing. That is, the included library is additionally expanded to the application installation destination, and the application's operational configuration setting file is rewritten. This will configure the application to use the additionally expanded bundled library. As a result, when the application platform executes the application, by using the additionally expanded bundled library, it is possible to ensure that there is no problem in the operation of the application (see, for example, Patent Document 1).

Patent No. 3613079

In such application platforms for embedded systems, some libraries included in the standard runtime determine operations based on the privileges of the called caller. Among such libraries, there are those that once decide on an action, they continue to execute the action without checking permissions.

At this time, if the first application has authority, when the library is called for the first time after the platform starts operating, the library determines its operation on the assumption that it has authority. If a second application that does not have the authority subsequently calls the library, the library operates with the authority of the second application and cannot execute the operation, causing a problem in operation. However, if the order is reversed, it can work without problems. In such cases, the library's behavior is determined by the privileges of the application that originally called it. If it is not clear which application will be called first, the entire platform may malfunction or not, resulting in instability.

Even if the technology of Patent Document 1 is used, this problem cannot be avoided in an application that is developed without knowing that the library has such a problem and is packaged in an installation medium.

The present invention has been made in view of the above conventional example, and it is an object of the present invention to allow a library that operates depending on the authority at the time of installation to operate appropriately even if it is called from an application having different authority.

In order to achieve the above object, the present invention has the following configuration, namely, according to one aspect of the present invention, a determining means for determining whether an application to be installed calls a specific library;
an installation unit that installs the application when the specific library is called, and further copies and installs the specific library in a location corresponding to the application;
a setting means for setting the application to preferentially call the specific library from a location where it was installed by the installation means;
An information processing device is provided that is characterized by having the following.

According to the present invention, a library that operates according to the authority at the time of installation can be operated appropriately even if it is called from an application having different authority. This has the effect of improving system stability and improving user convenience.

1 is a diagram showing the configuration of an application platform (105) of the present invention. 1 is a diagram showing the configuration of an application platform (105) of the present invention. 1 is a diagram showing the configuration of an application platform (105) of the present invention. It is a flowchart showing the operation of the installer (107) of the present invention. It is a diagram showing the directory structure of a second embodiment of the application platform (105) of the present invention. It is a flowchart representing the operation of the installer (107) of the second embodiment of the application platform (105) of the present invention. It is a flowchart representing the operation of the installer (107) of the second embodiment of the application platform (105) of the present invention. It is a flowchart representing the operation of the installer (107) of the third embodiment of the application platform (105) of the present invention. It is a flowchart representing the operation of the installer (107) of the third embodiment of the application platform (105) of the present invention.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the claimed invention. Although a plurality of features are described in the embodiments, not all of these features are essential to the invention, and the plurality of features may be arbitrarily combined. Furthermore, in the accompanying drawings, the same or similar components are designated by the same reference numerals, and redundant description will be omitted.

[First embodiment]
●Configuration of Image Forming Apparatus FIGS. 1A to 1C are diagrams showing the configuration of a first embodiment for implementing the present invention. FIG. 1A is a block diagram showing the configuration of an image forming apparatus 100, a controller 101, and a software module operating on the controller in the first embodiment. The application platform 105 of the first embodiment operates in the image forming apparatus 100. A controller 101 controls the operation of the image forming apparatus 100. Note that the image forming apparatus 100 is sometimes referred to as an information processing apparatus, focusing on its information processing function.

FIG. 1B is a diagram schematically showing the hardware configuration of the controller 101 of the image forming apparatus 100. A central processing unit (Central Processing Unit, hereinafter referred to as CPU) 120 executes a program stored in a memory such as a RAM 122 and processes data also stored in the RAM 122. The RAM 122 is a random access memory and stores, for example, programs and data. The ROM 123 is a read-only memory and stores, for example, programs and data. Although the ROM 123 is a nonvolatile memory, it may be rewritable by the CPU 120. A network interface (hereinafter abbreviated as I/F) 124 connects the system bus 121, which interconnects each component, to a network. Storage I/F 125 connects system bus 121 and storage device 126. Storage device 126 maintains secondary storage. The engine I/F 127 is an engine I/F for connecting the system bus 121 and the image forming engine 128 of the image forming apparatus 100. The engine 128 is an image forming engine provided in the image forming apparatus 100. The recording method of the engine 128 is, for example, an inkjet method or an electrophotographic method, but other methods may be used.

●Controller Software Returning to FIG. 1A, the software configuration of the controller 101 will be explained. The operating system 102 is an operating system that is the basis of software that implements information processing functions executed by the CPU 120 of the controller 101. The file system 103 is a file system that the operating system 102 constructs on the storage device 126 via the CPU 120 and storage I/F 125. Standard runtime 104 is a standard runtime used by application platform 105 to run applications 161, 162 and installer 107. The standard runtime is a software module that is installed in a standard manner to execute the applications 161, 162 and the installer 107, and is sometimes called a standard runtime engine, standard runtime module, or the like. Application platform 105 is a platform on which applications are installed and run. Specifically, for example, there is JAVA (registered trademark). Standard library 106 is one or more software libraries included in standard runtime 104.

Application 161 is a first application program installed and operated on application platform 105. Application 162 is a similar second application program. One or more applications represented by a first application 161 and a second application 162 can be installed on the application platform 105. In this embodiment, when describing the applications, a series of numbers starting from the application 161 are assigned, and the number notation "16n" is used as a representative number. The installer 107 is an installer for installing the application 16n on the application platform 105.

●File System FIG. 1C schematically illustrates the arrangement of files constituting the application platform 105 and the application 16n on the file system 103 of this embodiment.

Root 150 is the root of the file system. The standard runtime package group 151 is a standard runtime package group placed in a directory. The library standard package 152 is a first library standard package included in the standard runtime package group 151. The first library corresponds to library A in the figure. The library standard package 153 is also a second library standard package included in the standard runtime package group 151. The second library corresponds to library B in the figure. The standard runtime package group storage directory 154 is a directory for storing the standard runtime package group 151. The cache directory 155 is a subdirectory that holds an application installation directory 17n for installing the application 16n. The save directory 156 is a directory for saving a copy of the second library standard package 153 included in the standard runtime package group 151. The save package 157 is a copy of the second library standard package 153 included in the standard runtime package group 151.

The installation directory 17n is a directory into which files of the application 16n are expanded when installing the application 16n. The application body file 18n-1 is a file in which the body of the application 16n is stored. The application library package 18n-2 is a library package that was included with the application 16n when the application 16n was installed. The installer 107 expands the application library package 18n-2 into the installation directory 17n when installing the application 16n. In some cases, the application library package 18n-2 may be a different version of the first library standard package 152 included in the standard runtime package group 151. The application library package 18n-3 is a copy of the second library save package 157 used by the application 16n by the installer 107.

The configuration file 19n is a file that describes the identifier of the application 16n, a version number, a description regarding library reference, and the like. As an example, if the configuration file 19n includes a description regarding the application 16n, the application platform 105 operates as follows. That is, the application 16n does not read the first library standard package 152 included in the standard runtime package group 151 regarding the first library. Instead, the included application library package 18n-2 expanded by the installer 107 is read and used. However, for libraries that are not described here, if they exist in the standard runtime package group 151, they will be used.

●Processing procedure by installer FIG. 2 is a flowchart schematically showing the operation of the installer 107 of the first embodiment. The processes described in the flowchart are realized by the CPU 120 executing programs stored in the RAM 122, ROM 123, storage device 126, etc. of the controller 101. The process starts from step S201. In the description, the installer 107 is the main component, but the main component in terms of hardware is the CPU 120.

In step S202, the installer 107 first performs licensing processing for the application (referred to as target application) 16n to be installed. Here, it is confirmed that the installation package of the application 16n is correctly licensed. The licensing method will not be discussed in detail here.

When the license processing is completed (for example, if the granting of the license has been confirmed), the process of the installer 107 continues to proceed to step S203. In step S203, the installer 107 extracts necessary files from the installation package of the application 16n and expands them into the installation directory 17n. For example, if there are library packages included with the installation package, they will also be expanded in this step. The file expanded in this way is the application library package 18n-2.

In step S204, it is determined whether the application 16n calls the second library 153. If it has been called, the process advances to step S205. If it has not been called, the process advances to step S209. In step S205, it is determined whether a package that provides the same API as the standard package 153 of the second library has already been expanded in the application installation directory. If the library local package (ie, application library package) 18n-2 does not exist, the process advances to step S206. If it exists, the process directly advances to step S207.

In step S206, the installer 107 copies the second library save package 157 placed in the save directory 156 to the installation directory 17n of the application 16n. The process then advances to step S208.

When the process proceeds to step S207, the installer 107 next detects whether the configuration setting file 19n of the application 16n has the following settings. That is, this is a setting for loading the package 18n-3 placed in the installation directory 17n with priority over the standard package 153 of the second library when the application 16n is executed (this setting is also called local priority setting). If this exists, the process proceeds directly to step S209; otherwise, the process proceeds to step S208.

In step S208, the installer 107 adds the local priority setting to the configuration setting file 19n of the application 16n. If this local priority setting is added, when the application platform 105 starts the application 16n later, the application library package 18n-3 dedicated to the application 16n will be read as the second library. When the additional setting is completed, the process advances to step S209.
Installation of the application 16n is completed in step S209. Although nothing special is done in this step, information indicating completion may be set in a specific storage area.

In the following processing step S210, the installer 107 also determines whether it is necessary to install the next target application 16n. If necessary, the process returns to step S202 to execute the same process using the next application 16n as a new target application. If it is not necessary, the process advances to step S211 and the process of the installer 107 ends.

As we have seen so far, in this embodiment, for all applications 16n that are known to call the second library (library B), the second library is installed in a location corresponding to each target application. do. In this embodiment, the location is the application directory. Then, settings for reading the second library, that is, local priority settings are performed. As a result, each of these applications 16n reads the second library from the package 18n-3 in the respective installation directory 17n and operates. Therefore, each application operates by calling different entities from the same second library. As a result, when each copy of the second library is initialized (or installed), settings are made for each copy, and the settings are fixed. This avoids problems that can occur when a single entity is shared by multiple applications. The problem is as follows. In other words, if different applications 16n have different permissions, and the entities of the second library are the same, when the entities are initialized, they will operate according to the permissions of the applications installed with that library. is fixed. As a result, depending on the called application 16n, a fixed operation cannot be executed due to the difference in authority, resulting in a problem. According to the present embodiment, these second libraries 153 have an entity for each application 16n, so such problems do not occur.

To explain this using a specific example, for example, the ImageIO package of JAVA (registered trademark) corresponds to the second library package. For example, in OSGi, when the ImageIO package is called for the first time after startup, the permission to write to /tmp is determined according to the first called application. When the first application that is called has permission to write to /tmp, the ImageIO package creates a file in /tmp and continues processing while saving data there. On the other hand, if the application that is first called does not have permission to write to /tmp, the ImageIO package thereafter processes data in memory without accessing /tmp. In the former case, if an application that does not have permission to write to /tmp calls ImageIO, a security exception may occur, resulting in an error.

In this embodiment, when installing an application that calls an ImageIO package, the ImageIO package is copied and installed for each application. This way, a copy of each ImageIO package is installed for each application that calls it. This prevents a mismatch between the application's authority and the library's authority, and prevents problems such as errors caused by the mismatch.

Note that in this embodiment, the authority given to the application is a binary value indicating whether or not it is permitted, but the authority may have more levels or combinations as values.

[Second embodiment]
Next, a second embodiment of the present invention will be described with reference to figures. The configuration of the software module in the second embodiment is similar to that shown in FIG. 1A. Further, the hardware configuration of the controller 101 of the image forming apparatus 100 in the second embodiment is the same as that shown in FIG. 1B.

FIG. 3 schematically shows the arrangement of files constituting the application platform 105 and the application 16n on the file system 103 of this embodiment. This is an alternative to FIG. 1C of the first embodiment. Elements 150 to 157 and elements 17n, 18n-1, 18n-2, and 19n are the same as those shown in FIG. 1C, so their explanations will be omitted.

The installation directory 373 is a directory in which the application 3 is installed. Note that in this embodiment, the library B package corresponding to the application library package 182-3 does not exist at the location of the application library package 182-3 in FIG. 1C.

A first directory 301 is a directory in which library B is located. The added first package 302 of library B is the first package of library B placed on the first directory 301 where library B is placed. The second directory 303 is the directory where library B is located. The added second package 304 of library B is the second package of library B placed on the second directory 303 in which library B is placed. The installation directory 373 is a directory in which the application 3 is installed. The main file 383-1 of the application 3 is placed in the installation directory 373. The configuration file 393 of the application 3 is also placed in the installation directory 373.

In the following, application 2 references library B and has specific authority. At the time of initialization, library B refers to its specific authority and determines its subsequent operations. The specific authority is, for example, the authority to access a specific directory, and library B, which was initialized by application 2 that has that authority, performs operations after initialization on the premise that it can access that specific directory. decide. Furthermore, application 3 similarly references library B and does not have the above-mentioned specific authority. Library B, which has been initialized by application 3 that does not have that authority, determines its operations after initialization on the premise that the specific directory cannot be accessed. Although only application 2 and application 3 are illustrated here, there may be a plurality of applications that have authority and applications that do not have authority.

4A and 4B are flowcharts schematically showing the operation of the installer 107 according to the second embodiment of the present invention. The processes described in the flowchart are realized by the CPU 120 executing programs stored in the RAM 122, ROM 123, storage device 126, etc. of the controller 101. This is similar to FIG. 2 of the first embodiment. The process starts from step S401.

In step S402, the installer 107 first performs licensing processing for the application 16n to be installed. This is similar to step S202. When the license processing is completed, the process of the installer 107 continues to proceed to step S403. In step S403, the installer 107 extracts any necessary files from the installation package of the application 16n and expands them to the installation directory 17n or 37n.

In step S404, it is determined whether the application 16n calls the second library 153. If it has been called, the process advances to step S405; if it has not been called, the process advances to step S419.

In step S405, it is determined whether a package (local package) that provides the same API as the standard package 153 of the second library has already been expanded in the application installation directory 17n or 37n. If the local package of the second library does not exist in the installation directory, the process advances to step S406.

In step S406, the installer 107 determines whether the application has the authority to be referenced when determining the operation of the second library during initialization. If the user has the authority, the process proceeds to step S407; if the user does not have the authority, the process proceeds to step S412.

Proceeding to step S407, the installer 107 determines whether the first directory 301 for placing the second library package exists for the application for which it has authority. If it exists, the process advances to step S408. If it does not exist, the process advances to step S409.

In step S408, the installer 107 determines whether a second library package 302 for an application that has authority is placed in the first directory 301. If it has not been placed, the process advances to step S410. If the package 302 already exists, the process advances to step S411.

When the process proceeds to step S409, first, a new directory 301 is created in which to place the package 302 of the second library. When using the second library from an application that has authority, the second library placed in this directory 301 is used. The process then proceeds to step S410.

When the process advances to step S410, the installer 107 copies the second library's save package 157 to the first directory 301. The process then advances to step S411. Here, the discussion will proceed assuming that the installation directory of the application 16n that has authority is the installation directory 172 in FIG. 3.

Proceeding to step S411, the installer 107 adds a setting for preferentially reading out the second library package 302 for the authorized application to the configuration setting file 192 of the application 16n. The process then advances to step S419.

If it is determined in step S406 that the application 16n does not have authority, the process advances to step S412.

Proceeding to step S412, the installer 107 determines whether a second directory 303 exists for arranging a second library package for applications without authority. If it exists, the process advances to step S413. If it does not exist, the process advances to step S414.

In step S413, the installer 107 determines whether a second library package 304 for applications without authority is placed in the second directory 303. If it has not been placed, the process advances to step S415. If the package 302 already exists, the process advances to step S416.

When the process advances to step S414, first a new directory 303 is created in which to place the package 304 of the second library. When using the second library from an application that does not have authority, the second library placed in this directory 303 is used. The process then advances to step S415.

When the process advances to step S415, the installer 107 copies the save package 157 of the second library to the first directory 303. The process then advances to step S416. Here, the discussion will proceed assuming that the installation directory of the application 16n without authority is the directory 373 in FIG. 3.

Proceeding to step S416, the installer 107 adds a setting for preferentially reading out the second library package 304 for the authorized application to the configuration setting file 372 of the application 16n. The process then advances to step S419.

If the second library package has been expanded in the installation directory 17n or 37n in step S405, the installer 107 then proceeds to step S417.

In step S417, the installer 107 determines whether a setting is written in the configuration setting file 19n or 39n of the application to give priority to reading packages placed in the installation directory 17n or 37n. If it has been written, the process advances to step S419. If it has not been written, the process advances to step S418.

In step S418, settings for preferentially reading packages placed in the installation directory 17n or 37n are added to the application configuration file 19n or 39n, and the process advances to step S419. The application installation process is completed in step S419. The process then proceeds to step S420.

In step S420, the installer 107 determines whether it is necessary to install the next application 16n. If necessary, the process returns to step S402 to continue processing with the next application as a new target application. If it is not necessary, the process advances to step S421 and the entire process is completed.

As seen so far, in this embodiment, the following settings can be made for the application 16n that is known to call the second library. That is, packages 302 and 304 of the second library, which are different for applications that have authority and applications that do not have authority, are installed in locations corresponding to each authority. In this embodiment, the location is a directory determined in advance for each application authority. By configuring the second library to be called, the second library is separated into those that are initialized for applications that have permissions and those that do not. Each of them is initialized and operated separately. That is, when an application operates, it uses a copy of the second library initialized by the application. Therefore, even if each operation is fixed depending on whether the user has authority or not, problems will not occur due to authority because the application is always called only by applications that have the same authority. Furthermore, in the first embodiment, a second library package 18n-3 is placed on the installation directory 17n or 37n for each application 16n and used. In this case, a package is opened and operated by the number of applications that use the second library, so as the number of applications increases, there is a risk that a large amount of file descriptors, which are a finite resource, will be consumed. However, according to the second embodiment, the packages that are opened are only for applications that have permissions and applications that do not have permissions, so in addition to the effects of the first embodiment, file descriptor consumption can be suppressed. There is an advantage.

Note that in this embodiment, the authority given to the application is a binary value indicating whether or not it is permitted, but the authority may have more levels or combinations as values. In this case, in this embodiment, the second library is copied a number of times according to the value, and each copy is initialized by an application to which respective permissions are granted. This causes each copy of the second library to be initialized with each permission value and called by an application with matching permissions.

[Third embodiment]
Next, a third embodiment of the present invention will be described with reference to figures. The configuration of the software module in this embodiment is the same as that in FIG. 1A. The hardware configuration of the controller 101 of the image forming apparatus 100 in this embodiment is the same as that shown in FIG. 1B. The arrangement of files constituting the application platform 105 and the application 16n on the file system 103 of this embodiment is the same as that in FIG. 3.

5A and 5B are flowcharts schematically showing the operation of the installer 107 of this embodiment. The processes described in the flowchart are realized by the CPU 120 executing programs stored in the RAM 122, ROM 123, storage device 126, etc. of the controller 101. The process starts from step S501.

In step S502, the installer 107 first performs licensing processing for the application 16n to be installed. When the license processing is completed, the process of the installer 107 continues to proceed to step S503. In step S503, the installer 107 extracts any necessary files from the installation package of the application 16n and expands them to the installation directory 17n or 37n.

In step S504, it is determined whether the application 16n calls the second library 153. If it has been called, the process advances to step S505; if it has not been called, the process advances to step S521.

Proceeding to step S505, the installer 107 determines whether the application has specific authority. The second library refers to its authority at the time of its initialization and determines its operations after initialization. This is similar to the second embodiment. If the user has the authority, the process proceeds to step S506; if the user does not have the authority, the process proceeds to step S513.

In step S506, the installer 107 determines whether the first directory 301 exists in which to place the second library package for the application that has the authority. If it exists, the process advances to step S507. If it does not exist, the process advances to step S508.

In step S507, the installer 107 determines whether the library package 302 in the second directory is placed in the first directory 301 for applications that have authority. If it has not been placed, the process proceeds to step S509; if it has been placed, the process proceeds to step S510.

In step S508, the installer 107 creates a new directory 301 in which to place the second library package for the application that has authority. When the creation is completed, the process advances to step S509.

In step S509, the save package 157 of the second library is copied to the directory 301. A directory 301 is a directory in which a package 302 used by an application having authority is placed. When the copying is completed, the process advances to step S510.

In step S510, a check is made to see if the configuration setting file 19n or 39n of the application contains a setting for preferentially reading a package placed in the directory 17n or 37n where the application is installed. If it has been written, the process advances to step S511. If it has not been written, the process advances to step S512.

In step S511, the installer 107 deletes the setting for preferentially reading from the configuration setting file 19n or 39n. In this case, in step S512, the settings for the application to preferentially call the second library are reset.

In step S512, the installer 107 adds to the configuration setting file 19n or 39n a setting for preferentially reading from the directory 301 in which the second library package 302 is placed, for an application having authority. The process then proceeds to step S520.

If the application 16n does not have authority in step S505, the process advances to step S513. In step S513, the installer 107 determines whether a second directory 303 exists for arranging a package of the second library for applications without authority. If it exists, the process advances to step S514. If it does not exist, the process advances to step S515.

In step S514, the installer 107 determines whether a second library package 303 for applications without authority is placed in the second directory 303. If it has not been placed, the process proceeds to step S516; if it has been placed, the process proceeds to step S517.

In step S515, the installer 107 creates a new directory 303 in which to place the second library package for applications without authority. When the creation is completed, the process advances to step S516. In step S516, the save package 157 of the second library is copied to the directory 303. When the copying is completed, the process advances to step S517.

In step S517, it is checked whether the configuration setting file 19n or 39n of the application contains a setting for preferentially reading the package placed in the directory 17n or 37n where the application is installed. If it has been written, the process advances to step S518. If it has not been written, the process advances to step S519.

In step S518, the installer 107 deletes the setting for preferentially reading from the configuration setting file 19n or 39n.

In step S519, the installer 107 adds, to the configuration setting file 19n or 39n, a setting for preferentially reading from the directory 301 in which the second library package 304 is placed, for an application having authority. The process then proceeds to step S520. The application installation process is completed in step S520. The process then proceeds to step S521.

In step S521, the installer 107 determines whether it is necessary to install the next application 16n. If necessary, the process returns to step S502 to continue processing with the next application as a new target application. If it is not necessary, the process advances to step S522 and the entire process is completed.

As seen so far, in this embodiment, the following settings can be made for the application 16n that is known to call the second library. That is, by setting different packages 302 and 304 to be called depending on whether the user has the authority or not, the second library is separated for applications that have the authority and applications that do not have the authority. Each of them is initialized and operated separately. Even if each operation is fixed depending on whether it has authority or not, it will always be called only by applications with the same authority, so problems will not occur due to authority.

Furthermore, in the second embodiment, there is a case where the second library package 18n-3 is placed on the installation directory 17n or 37n of the application 16n, and the application 16n uses it. When there is a certain number of such applications 16n, they open and call local packages, which causes a problem in that they consume file descriptors, which are finite resources, by the number of applications 16n. Even in such a case, according to the present embodiment, the setting for calling a local package for each application is canceled, and those placed in the common directories 301 and 303 are used. Therefore, even if the number of applications that use the second library increases, there is an advantage that the consumption of file descriptors is always kept to a minimum.

Note that in this embodiment, as in the second embodiment, the authority of the application is not binary, but may be multi-valued authority having many levels or combinations as values. In this case, in this embodiment, the second library is copied a number of times according to the value, and each copy is initialized by an application to which respective permissions are granted. This causes each copy of the second library to be initialized with each permission value and called by an application with matching permissions.

●Summary of the embodiments The above embodiments can be summarized into the following items.
(Item 1)
a determining means for determining whether an application to be installed calls a specific library;
an installation unit that installs the application when the specific library is called, and further copies and installs the specific library in a location corresponding to the application;
a setting means for setting the application to preferentially call the specific library from a location where it was installed by the installation means;
An information processing device comprising:
(Item 2)
The information processing device according to item 1,
An information processing device characterized in that the location corresponding to the application is the same directory as the application.
(Item 3)
The information processing device according to item 1,
The information processing apparatus is characterized in that the installation means copies and installs the specific library in a location corresponding to the authority granted to the application, as a location corresponding to the application.
(Item 4)
The information processing device according to item 3,
When the application is set to call the specific library that is installed in the same directory as the application, the setting means allows the application to access the specific library with the authority granted to the application. An information processing device characterized in that the information processing device is configured to reset the setting to preferentially call from a location corresponding to the location.
(Item 5)
The information processing device according to item 3,
An information processing device characterized in that the authority includes an authority to access a specific resource.
(Item 6)
The information processing device according to any one of items 1 to 5,
The information processing apparatus is characterized in that the specific library is a library whose operation is determined according to authority granted to the application when it is installed by the installation means.
(Item 7)
The information processing device according to any one of items 1 to 5,
further comprising storage means for storing the specific library as a source for copying the specific library;
The information processing apparatus is characterized in that the installation means reads the specific library from the storage means and copies it.
(Item 8)
The information processing device according to any one of items 1 to 5,
An information processing apparatus characterized in that a library other than the specific library is installed at a predetermined location.
(Item 9)
A method for installing an application by an information processing device, the information processing device having a determination means, an installation means, and a setting means,
The determining means determines whether the application to be installed calls a specific library,
The installation means installs the application when the specific library is called, and further copies and installs the specific library in a location corresponding to the application,
The installation method is characterized in that the setting means sets the application to preferentially call the specific library from a location where it is installed by the installation means.
(Item 10)
The installation method described in item 9,
The installation method is characterized in that the location depending on the application is the same directory as the application.
(Item 11)
The installation method described in item 9,
The installation method is characterized in that the installation means copies and installs the specific library in a location corresponding to the authority granted to the application, as a location corresponding to the application.
(Item 12)
The installation method described in item 11,
When the application is set to call the specific library that is installed in the same directory as the application, the setting means allows the application to access the specific library with the authority granted to the application. An installation method characterized by reconfiguring settings to preferentially call from a location corresponding to .
(Item 13)
A program for causing a computer to function as the information processing device according to any one of items 1 to 8.

[Other Examples]
The present invention provides a system or device with a program that implements one or more of the functions of the embodiments described above via a network or a storage medium, and one or more processors in the computer of the system or device reads and executes the program. This can also be achieved by processing. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

The invention is not limited to the embodiments described above, and various changes and modifications can be made without departing from the spirit and scope of the invention. Therefore, the following claims are hereby appended to disclose the scope of the invention.

100 image forming apparatus, 101 controller, 102 operating system, 103 file system, 104 standard runtime, 105 application platform, 106 standard library, 107 installer

Claims (13)

a determining means for determining whether an application to be installed calls a specific library;
an installation unit that installs the application when the specific library is called, and further copies and installs the specific library in a location corresponding to the application;
a setting means for setting the application to preferentially call the specific library from a location where it was installed by the installation means;
An information processing device comprising: The information processing device according to claim 1,
An information processing device characterized in that the location corresponding to the application is the same directory as the application. The information processing device according to claim 1,
The information processing apparatus is characterized in that the installation means copies and installs the specific library in a location corresponding to the authority granted to the application, as a location corresponding to the application. The information processing device according to claim 3,
When the application is set to call the specific library that is installed in the same directory as the application, the setting means allows the application to access the specific library with the authority granted to the application. An information processing device characterized in that the information processing device is configured to reset the setting to preferentially call from a location corresponding to the location. The information processing device according to claim 3,
An information processing device characterized in that the authority includes an authority to access a specific resource. The information processing device according to any one of claims 1 to 5,
The information processing apparatus is characterized in that the specific library is a library whose operation is determined according to authority granted to the application when it is installed by the installation means. The information processing device according to any one of claims 1 to 5,
further comprising storage means for storing the specific library as a source for copying the specific library;
The information processing apparatus is characterized in that the installation means reads the specific library from the storage means and copies it. The information processing device according to any one of claims 1 to 5,
An information processing apparatus characterized in that a library other than the specific library is installed at a predetermined location. A method for installing an application by an information processing device, the information processing device having a determination means, an installation means, and a setting means,
The determining means determines whether the application to be installed calls a specific library,
The installation means installs the application when the specific library is called, and further copies and installs the specific library in a location corresponding to the application,
The installation method is characterized in that the setting means sets the application to preferentially call the specific library from a location where it is installed by the installation means. The installation method according to claim 9,
The installation method is characterized in that the location depending on the application is the same directory as the application. The installation method according to claim 9,
The installation method is characterized in that the installation means copies and installs the specific library in a location corresponding to the authority granted to the application, as a location corresponding to the application. The installation method according to claim 11,
When the application is set to call the specific library that is installed in the same directory as the application, the setting means allows the application to access the specific library with the authority granted to the application. An installation method characterized by reconfiguring settings to preferentially call from a location corresponding to . a determining means for determining whether an application to be installed calls a specific library;
an installation unit that installs the application when the specific library is called, and further copies and installs the specific library in a location corresponding to the application;
a setting means for setting the application to preferentially call the specific library from a location where it was installed by the installation means;
A program that allows a computer to function.

Images