Moderators, translator
455
edits
Difference between revisions of "Switching Branches"
Yet a rephrase of the unstable definitions - clarifying - it is Manjaro specific packages which is considered unstable in unstable branch
(Rephrased the paragraphs on testing and unstable - changed boxes) |
(Yet a rephrase of the unstable definitions - clarifying - it is Manjaro specific packages which is considered unstable in unstable branch) |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
{{Important|Manjaro specific packages downloaded and installed from the ''Testing branch'' or ''Unstable branch'' will, by nature, not have been fully tested, and may be unstable. | |||
Please refer to [[System Maintenance]] Section for important maintenance information. | |||
}} | |||
One of the many features that sets Manjaro apart from other Arch-based distributions is that it uses its own dedicated software branches, rather than relying on those provided by Arch itself. In fact, to ensure continued stability and reliability, Manjaro actually uses three distinct branches: | One of the many features that sets Manjaro apart from other Arch-based distributions is that it uses its own dedicated software branches, rather than relying on those provided by Arch itself. In fact, to ensure continued stability and reliability, Manjaro actually uses three distinct branches: | ||
* '''Stable branch''': | * '''Stable branch''': The packages that come to stable have gone through roughly a couple of weeks testing by the users of the ''Unstable/Testing'' repos, before they get the packages. These packages are usually free of any problems. | ||
* '''Testing branch''': | * '''Testing branch''': This is the second line of defense. Being a larger number of users than those using ''Unstable'', they refine the work done prior to them by providing feedback on the packages they recieve on updates. | ||
* '''Unstable branch''': is synced several times a day with Arch package releases. Only a subset of Arch packages are modified to suit Manjaro. Those that use ''Unstable'' need to have the skills to get themselves out of trouble when they | * '''Unstable branch''': Unstable is synced several times a day with Arch package releases. Only a subset of Arch packages are modified to suit Manjaro. Those that use ''Unstable'' need to have the skills to get themselves out of trouble when they move their system to this branch. They are the Manjaro users who are most likely to need to use such skills. Due to the feedback from the users of the ''Unstable'' repo, many issues are catched and fixed at this level. Although the very latest software will be located here, <u>using the ''unstable branch'' is usually safe but - in rare cases - may cause issues with your system!</u> | ||
'''Summing up''', | '''Summing up''', Manjaro packages start their lives in the ''unstable'' branch. Once they are a deemed stable, they are moved to the ''testing'' branch, where more tests will be realized to ensure the package is ready to be submitted to the ''stable'' branch. | ||
{{BoxSecondary|Note on unstable branch| | {{BoxSecondary|Note on unstable branch|Remember: ''unstable'' branch comes directly from Arch Linux's stable branch. Manjaro specific packages such as kernels, kernel modules and Manjaro applications enter the repo with this branch and it is those packages which are considered unstable when they enter - not Arch packages as they are considered stable.}} | ||
== Changing to another branch == | == Changing to another branch == | ||