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

Revision as of 12:37, 7 November 2020

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

The system *must* roll forward as unit so it difficult to hold any individual package at an older version without breaking your system
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