Slots and Subslots

Slots and Subslots are mechanisms used in Gentoo's Portage package management system to allow multiple versions or variants of the same software to coexist on a single system without conflicts. This system provides fine-grained control over package versioning, dependencies, and upgrade paths by separating packages into different "slots" and further refining that separation with "subslots."

Slots

Slots are identifiers attached to packages that signify mutually incompatible versions or variants. When a package is installed into a specific slot, it guarantees that no other package installed in the same slot can coexist with it, because they might overwrite the same files or provide conflicting functionality. However, packages installed in different slots can coexist without interference.

Slots enable multiple versions of a package to be installed simultaneously. For example, a library might offer both version 1 and version 2 under separate slots—slot 1 and slot 2 respectively. This is useful when different applications depend on different versions of the same library.

Slots are declared in the ebuild metadata, typically as a string or number representing the major version or a variant type. Portage uses this information to manage package installations, upgrades, and dependency resolution.

Slot Syntax and Usage

Slots are specified in an ebuild's metadata using the SLOT variable, which usually contains a simple identifier:

SLOT="1"

or

SLOT="2"

Multiple slots can be declared if the ebuild supports multiple variants or versions within the same package category.

Slot Impact on Dependencies

Dependencies can specify which slot of a package they require, allowing for precise control over required versions. For example:

dev-libs/libfoo:1

means that the dependency requires slot 1 of libfoo. This ensures that the correct version is installed for compatibility.

Subslots

Subslots are an extension of slots that provide a more granular differentiation within a slot. While slots differentiate major incompatible versions or variants, subslots allow tracking of minor version changes or ABI (Application Binary Interface) changes that do not require a full slot change but still influence dependency compatibility.

Subslots are typically used when a package's ABI changes in a backward-compatible way or when minor updates require dependent packages to be rebuilt or updated.

Subslot Syntax and Usage

Subslots are defined implicitly by the package version or explicitly using the SLOT syntax with a colon separator. The subslot is derived from the first part of the version string after the slot.

For example, if a package has:

SLOT="1"

and the version is 1.2.3, the subslot would be 1.2 by default (major and minor version). Different subslots within the same slot represent different ABI versions.

Role of Subslots in Dependency Management

Subslots allow Portage to detect when a package needs to be rebuilt due to ABI changes in its dependencies, even if the slot remains the same. For example, if a library updates from ABI 1.2 to 1.3, packages depending on it may require recompilation or updating.

Dependencies can specify subslot requirements, ensuring that dependent packages are compatible with the precise ABI version of the dependency.

Practical Example

Consider a shared library libbar with the following versions:

• Version 1.0.0, ABI 1.0
• Version 1.2.0, ABI 1.2
• Version 2.0.0, ABI 2.0

libbar uses slots to separate major versions:

• Slot 1 for all version 1.x.y releases
• Slot 2 for version 2.x.y releases

Within slot 1, subslots differentiate ABI changes:

• Subslot 1.0 for 1.0.0
• Subslot 1.2 for 1.2.0

This setup allows:

• Installation of both libbar slot 1 and slot 2 simultaneously.
• Portage to know that when upgrading from 1.0.0 to 1.2.0, dependent packages may require rebuilding due to ABI changes reflected by subslot updates.

Benefits of Slots and Subslots

• Multiple version coexistence: Different major versions of the same package can be installed simultaneously.
• Precise dependency control: Dependencies can specify exact slot and subslot requirements.
• Efficient upgrades: Portage can determine which packages need rebuilding based on ABI changes indicated by subslots.
• Reduced conflicts: Avoids file overwrites and incompatibility issues between different package versions.
• Fine-grained versioning: Allows seamless management of major and minor changes within the package ecosystem.

Summary of Key Concepts

Conclusion

Slots and subslots provide a robust and flexible mechanism in Gentoo's Portage to manage multiple versions of packages and their dependencies. Slots distinguish fundamentally incompatible versions or variants, while subslots allow finer control within those versions, particularly to handle ABI changes and ensure proper rebuilds. This system ensures stability, flexibility, and precision in package management.