Jump to: navigation, search

Virtual Packages

824 bytes added, 6 years ago
Common uses for virtual packages: libraries
While the tools don't necessarily need to be fully compatible, they need to have a common basic usage. In particular, when a tool from one provider is replaced by a tool from another, the reverse dependencies must remain in working state, with no need for rebuilds or configuration adjustments.
=== Libraries with certain degree of ABI compatibility ===
Example: ''virtual/libudev''
This kind of virtuals is to allow switching between multiple providers of a library. However, virtual can only be used when the various providers provide ABI-compatible variants of the same library.
Virtual ebuild should have a separate version at least for every ABI version of the library. The ebuilds should have appropriate subslots and depend on respective subslots or versions of the provider that provide the library with necessary ABI. For example, virtual/libfoo-1 depends on specific versions of libfoo providers that provide, while virtual/libfoo-2 depends on versions providing This guarantees that the reverse dependencies of the virtual will be rebuilt when the underlying library is upgraded.

Navigation menu