Long chains of dependencies If app depends on liba, which depends on libb. This is a particular problem if an application uses a small part of a big library (which can be solved by code refactoring), or a simple application relies on many libraries. This is partly inevitable an application built on a given computing platform (such as Java) requires that platform to be installed, but further applications do not require it. It can also be difficult to locate all the dependencies, which can be fixed by having a repository (see below). Many dependencies An application depends on many libraries, requiring lengthy downloads, large amounts of disk space, and being very portable (all libraries are already ported enabling the application itself to be ported easily). This, in turn, may break other dependencies and push the problem to another set of packages. If the shared package or library can only be installed in a single version, the user may need to address the problem by obtaining newer or older versions of the dependent packages. The dependency issue arises when several packages have dependencies on the same shared packages or libraries, but they depend on different and incompatible versions of the shared packages. Colloquial term for software requiring many conflicting dependenciesÄependency hell is a colloquial term for the frustration of some software users who have installed software packages which have dependencies on specific versions of other software packages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |