![]() Either use edge or stable.Īfter upgrading to edge, the currently installed edge version may be checked withĪnd referring to the build date that is attached to the release. Warning: Do not enable stable and edge repos at the same time. The crucial difference is, that when editing the /etc/apk/repositories file, all referenced repository versions (such as v3.2 or latest-stable) therein need to be pointing to edge as in: Testing edge is a great way to contribute to the Alpine Linux development.Īn upgrade of Alpine Linux from a stable version to the rolling development version edge basically requires the same steps as Upgrading to latest release. However, testing edge is a very valuable activity which helps the Alpine Linux development to ensure that the quality of the stable releases is high. Because edge is a development branch, many changes are not heavily tested (or tested at all) and packages in edge can and sometimes do break without warning. It is possible that bugs in edge could cause data loss or could break your system.Įnd users should not use edge as their main day-to-day workstation or as a productive system. Warning: edge is under constant development so be careful using it in production. Those packages are updated on a regular basis. It consists of an APK repository called edge and contains the latest build of all available Alpine Linux packages. After that you will need to update to the new release to continue to have support.Įdge is the name given to the current development tree of Alpine Linux. community has a maximum support cycle of 6 months. The community repository was introduced with Alpine Linux version 3.3.0. Packages in main must not have dependencies in other repositories. We also try to limit the amount of packages in main to only include base system packages, in base you can think of packages which are needed by other packages or are needed to setup a basic system. Security fixes beyond that can be made on request when there are patches available. The main repository is typically supported for 2 years and the community repository is supported until next stable release. Each May and November we make a release branch from edge. There are several release branches for Alpine Linux available at the same time. Warning: Changing the repositories to latest-stable may initiate unexpected release upgrades. ![]() A tagged repository is prefixed with the specifier, followed by a space and the repository location. The location may be an or URL, or the path to a directory on the local filesystem. Lines that start with a hash character (#) are ignored. Each line of this file specifies the location of a package repository, and optionally a tag. The package repositories that apk uses to retrieve package files for installation are specified in file /etc/apk/repositories. Packages from testing that are accepted go to the community repository or (rarely) the main repository. The testing repository is only available on edge. These are made by any contributor to Alpine. testing packages are where new packages go.Packages from testing that are accepted go to the community repository. They are supported by those user(s) contributions and could end if the user(s) stops they may also be removed in a future release due to lack of support by upstream authors. community packages are those made by users in team with the official developers and close to the Alpine package process.Packages from community or (rarely) testing, that are accepted go to the main repository. Commonly these packages are selected due to their responsibility and stability with respect to upstream availability. They also have official special documentation, are always available for all releases and will have substitutions if some are not continued from upstream. main packages are the software that have direct support and updates from the Alpine core and main team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |