Difference between revisions of "Translations:The Rolling Release Development Model/6/es"

Latest revision as of 10:15, 6 August 2021

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (The Rolling Release Development Model)

* The system ''must'' roll forward as a unit so it's difficult to hold any individual package at an older version without breaking your system eventually
* Since everything is being updated when updates are available it is a challenge to run a rolling release distro in an environment where bandwidth is extremely limited
* You must update your system before installing software. Not doing so can leave your system in an inconsistent, partially upgraded state

* The system ''must'' roll forward as a unit so it's difficult to hold any individual package at an older version without breaking your system eventually
* Since everything is being updated when updates are available it is a challenge to run a rolling release distro in an environment where bandwidth is extremely limited
* You must update your system before installing software.  Not doing so can leave your system in an inconsistent, partially upgraded state

El sistema *debe* lanzar continuamente todo como una unidad, por lo cual dificulta tomar un paquete individual en una versión antigua sin cortar el sistema.
Como todo se actualiza cuando las actualizaciones se encuentran disponibles, es un reto arrancar una distribución de lanzamiento continuo donde el ancho de banda es extremadamente limitado.
Debe actualizarse el sistema antes de instalar el software. No hacerlo puede causar que el sistema quede en un estado inconsistente y parcialmente revaluado.