Difference between revisions of "The Rolling Release Development Model/ru"
Views
Actions
Namespaces
Variants
Tools
(Created page with "Каковы преимущества rolling модели?") Tags: Mobile web edit Mobile edit |
(Created page with "* Вам никогда не потребуется '''глобальное обновление''' системы. Просто продолжайте запускать не...") Tags: Mobile web edit Mobile edit |
||
Line 6: | Line 6: | ||
Обзор трех репозиториев, которые Manjaro использует для управления своими пакетами, можно найти [[Manjaro:_A_Different_Kind_of_Beast/ru#Раздельные_репозитории|здесь]] | Обзор трех репозиториев, которые Manjaro использует для управления своими пакетами, можно найти [[Manjaro:_A_Different_Kind_of_Beast/ru#Раздельные_репозитории|здесь]] | ||
{{SectionTemplate|Каковы преимущества rolling модели?| | {{SectionTemplate|Каковы преимущества rolling модели?| | ||
* | * Вам никогда не потребуется '''глобальное обновление''' системы. Просто продолжайте запускать небольшие '''обновления''' как обычно, и вы всегда будете иметь последнюю версию. | ||
* | * Последняя версия всех пакетов программного обеспечения всегда доступна - нет необходимости прибегать к привязкам или flatpaks для запуска текущего программного обеспечения. | ||
}} | }} | ||
Revision as of 07:11, 29 December 2022
Обзор трех репозиториев, которые Manjaro использует для управления своими пакетами, можно найти здесь
- Вам никогда не потребуется глобальное обновление системы. Просто продолжайте запускать небольшие обновления как обычно, и вы всегда будете иметь последнюю версию.
- Последняя версия всех пакетов программного обеспечения всегда доступна - нет необходимости прибегать к привязкам или flatpaks для запуска текущего программного обеспечения.
- 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
It would seem that some confusion has arisen due to the regular (and somewhat rapid) occurrence of new Manjaro releases. This confusion has been compounded still further by the use of version numbers (for example: 18.0.2,18.1 and so on), a custom normally associated with the Standard Release Development Model, where a brand-new release of an operating system must be re-installed over an old version in order to access any new features provided. These releases are more accurately new snapshots of the Manjaro system. Just like photographs, these snapshots are in essence images that portray the Manjaro system at a particular point in its development. As such, one purpose they serve is to help the developers to both chart and evaluate the continued development of the Manjaro system, as it is of course easier to pick up on the finer details from a single image than from a moving picture.
Since Manjaro is constantly rolling forward, a snapshot of the Manjaro system will very quickly become out of date. New snapshots are therefore released in order to make life easier for new users, who may otherwise be faced with the prospect of downloading huge volumes of new software packages to update and upgrade their newly installed systems from an older ISO.
Where these snapshots most obviously differ is in the choice of pre-installed software applications provided, as well as other smaller tweaks such as the default themes used, However, the core Manjaro system running underneath is the same and any applications added or removed from a particular snapshot can also be added or removed from an existing installation. And, of course, users will tweak and customise their own systems in accordance with their own personal preferences and tastes, anyway. Again, it is not important which release of Manjaro was initially installed. Provided it is kept up to date, that system will always be running the latest version available.