Enable Community Repository

#REDIRECT Repositories#Enabling_the_community_repository
Alpine software repositories have main packages and contributions made. Each Alpine release has two branches of repositories. The /community repository of each Alpine release contains community supported packages that were accepted from the /testing repository. Only /main repository of each version of Alpine release are supported for some Main Alpine Developers and Man Powers.
* Main packages are the Alpine package software that have direct support and updates from the Alpine core and main team, also have official documentation. Are always available for all releases and will have substitutions if some are not continued from upstream. Commonly those packages are selected due their responsibility and stability respecting upstream availability. Packages from testing that performs well or are mature goes to main branch.
* Community packages are those made by users in team with the official developers and well near integrated to the Alpine packages. Those have supported by those user contributions and could end if the user also ends respect with Alpine work, but may be removed in a future release due lack of support by upstream author. Packages from testing that are accept goes to community branch.
* Testing packages come into testing or edge repositories and are those made by any contributor on Alpine, the edge, this branch of repository has no release linked or related of Alpine. Those are in edge and when accepted goes to testing.
== Using community repositories ==
The community repository was introduced with Alpine Linux version 3.3.
To enable the repository, edit the file and add (or uncomment) a line that points to the "community" directory.
Its format is:
https://<mirror-server>/alpine/<version>/community
After enabling the community repository, one needs to update the index of available packages with:
And then it's possible to install packages from the community repository.
=== Adding community repositories with a script ===
The following commands will add the main and community repositories for the Alpine version you're using. It will overwrite your existing repository settings.
Dont forget to run this after:.
== Using specific package versions ==
You can specify or pin "sticky" package versions like this:
* apk add packagename=1.2.3-suffix
* apk add 'packagename<1.2.3-suffix'
That will upgrade these packages only until the specified version.
It's then safe to use apk upgrade to upgrade all packages, while packages with versions will remain on the specified version.
To set a minimum version just add ….
== Using testing repositories ==
The testing repository was introduced with Alpine Linux edge development. To enable the repository, edit the file using an editor ( for instance) and add a line that points to the "testing" directory, formatted as in:
https://<mirror-server>/alpine/edge/testing
After enabling the testing repository, one needs to obtain the latest index of available packages with:
Inexperienced users should not enable this.
=== Using packages from testing (edge) ===
Never pin packages from the "edge" branch of the alpine package repo, as these are in test and may be revoked. (At pkgs.alpinelinux.org/packages, click "edge" and change it to the alpine image version you use, and click "search" again.)
Inexperienced users should not enable this.
= See also =
Category:Package Manager