Manjaro Das Entwicklungsmodel "Rolling Release"

Das Entwicklungsmodel "Rolling Release"

From Manjaro
Revision as of 13:18, 7 September 2021 by Andreas85 (talk | contribs) (Created page with "Warum werden neue Versionen von Manjaro veröffentlicht?")
Other languages:
Deutsch • ‎English • ‎Türkçe • ‎español • ‎français • ‎русский • ‎فارسی
Manjaro verwendet ein Rolling Release Entwicklungs-Model, bei dem das Kernsystem nicht ersetzt, sondern kontinuierlich aktualisiert wird. Daher ist es nicht notwendig, eine spätere Version von Manjaro erneut zu installieren, um das allerneueste und aktuellste System zu genießen. Da eine vorhandene Installation immer wieder aktualisiert wird, wird bereits die neueste Version ausgeführt.

Eine Übersicht über die drei Repositories, die Manjaro zur Verwaltung seiner Pakete verwendet, finden Sie hier

Was sind die Vorteile eines rollenden Modells?

  • Sie müssen nie System-Upgrades durchführen. Führen Sie die Updates einfach wie gewohnt aus und Sie werden immer auf der neuesten Version sein
  • Die neueste Version aller Softwarepakete ist immer verfügbar, Sie müssen nicht auf Snaps oder Flatpaks zurückgreifen, um aktuelle Software auszuführen

Was sind die Nachteile eines Rolling-Release-Modells?

  • Das System *muss* als Einheit vorwärtsrollen, so dass es schwierig ist, einzelne Pakete in einer älteren Version zu halten, ohne Ihr System zu beschädigen
  • Da alles aktualisiert wird für das Updates verfügbar sind, ist es eine Herausforderung, eine Rolling-Release-Distribution in einer Umgebung mit extrem begrenzter Bandbreite zu betreiben
  • Sie müssen Ihr System aktualisieren, bevor Sie Software installieren. Andernfalls kann sich Ihr System in einem inkonsistenten, nur teilweise aktualisierten Zustand befinden

Warum werden neue Versionen von Manjaro veröffentlicht?

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.

Why are new releases given version numbers?

Quite simply, version numbers have been assigned to snapshots of Manjaro by the developers to help them clearly mark each stage of its development. They also help differentiate between the ISO files released at certain periods of time.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.