![]() | Name | Last modified | Size | Description |
---|---|---|---|---|
![]() | Parent Directory | - | ||
![]() | backports/ | 2025-03-10 15:11 | - | |
![]() | experimental/ | 2025-02-06 15:54 | - | |
![]() | stable/ | 2025-02-06 16:04 | - | |
![]() | testing/ | 2025-02-06 15:56 | - | |
![]() | unstable/ | 2025-02-06 15:52 | - | |
![]() | README.html | 2025-03-10 13:50 | 2.1K | |
Suite represents a snapshot of a set of packages at a modeled level of maturity.
In Regolith the following suites from least-stable to most-stable are modeled:
- experimental
- For packages and changes that may be reverted, removed, or change
significantly over time. Serious bugs are common and expected here.- unstable
- For packages and changes that are planned to reach a release but
have yet to undergo much testing. Serious bugs may occur from time
to time. Regolith core developers may run their testing and development
from this stage but users are discouraged from consuming packages
from unstable.- testing
- For packages undergoing testing by Regolith developers and early
adopters. Bugs occur but serious bugs should not often pop up in
this stage. Regolith users that wish to get access to fixes and new
features earlier may consume from this stage with the understanding
that bugs are to be expected (and reporting them is appreciated!)- backports
- For packages that have been released under "stable" suite and are
now needed to be ported back to the older releases, or distros. Most
of the time there is no general need to use these archive, as all of
the packages in this archive already exist in stable.- stable
- For packages that have been determined to be suitable for general
use. While minor bugs may be present in packages at this stage, the
bugs present should not interfere with general use of the environments
for users on supported distros and releases.
Please refer to Anatomy of the Regolith apt Config Line for more information on
how to correctly set up apt to use these archives.