Complemento de Modularidad de Fedora

Modularidad Fedora introduce un repositorio Modular opcional que suministras versiones adicionales de software sobre ciclos de vida independientes.

Los usuarios pueden mantener ahora su sistema operativo actualizado mientras tiene mientras tiene la versión correcta de una aplicación para su caso de uso, incluso cuando cambia la versión predeterminada en la distribución.

Características

Este cambio introduce tres nuevos repositorios opcionales para versiones adicionales de software entregados como flujos de módulos.

Los módulos son colección de paquetes que representan una aplicación, una pila de idiomas o una colección de paquetes que tiene sentido que se entreguen juntos. Un ejemplo podría ser un módulo nodejs.

Los flujos son series de versiones que son compatibles con versiones anteriores. Un ejemplo podria ser dos flujos de nodejs — versión 6.x y versión 8.x compatible.

Client tooling (DNF) has been improved to be able to manage multiple streams of software. Users can choose the right stream for their use case and DNF makes sure that:

  • The right versions of packages get installed.

  • Updating the system also updates the packages within the module streams to their latest versions.

  • Updating the system will never cause a module to skip to another stream, even when there are newer versions available. Changing streams is always a conscious decision the user explicitly makes.

Should users choose not to bother with modules and streams, they always get the distribution default. This means that modularity can be used without any changes to the existing workflows.

Also, upgrading an existing Fedora installation won’t require any special steps as there are no changes to the main Fedora repository. The new content is in a separate repository that is completely optional.

What are the benefits?

Different users have different needs. Developers want the latest versions possible, system administrators want stability for longer period of time.

Modularity makes some parts of the system to move slowly, and other parts to move faster — so users can choose the right speed of different parts according to their use case.

Next steps

Modules can have independent lifecycles from the base Fedora release. Starting next release, it will be possible to build modules against multiple Fedora releases thanks to the Stream Expansion functionality.

That means users will be able to upgrade to the new Fedora version while keeping the streams of software they need for their applications. This will be particularly useful for Fedora Server.