Community recipes

sps-community is a third recipe tree. It is hosted next to core and extra, uses the same SPS format, and is not enabled by setup, mkiso, or a fresh install. Core (priority 100) and extra (80) are. Community uses priority 50, so an official package of the same name always wins.

That is the Alpine-style split: the distro ships the official collections; you add community yourself.

Enable it

Edit /etc/sps/repos.conf. A generated file already has these two lines commented. Uncomment the git line, or append it:

git community https://github.com/RobertFlexx/sps-community.git 50

On a machine that still uses bundled dir trees:

dir core /usr/src/sps/core 100
dir extra /usr/src/sps/extra 80
git community https://github.com/RobertFlexx/sps-community.git 50

Then:

src update
src search PATTERN
sget info PACKAGE
sget install PACKAGE

src update clones the checkout to /usr/src/sps/community. Removing the git line and running src update again drops community from the index. Delete the checkout if you want it off disk.

Do not raise community above extra or core. Do not reuse a package name that already exists in those trees.

What it is for

Software that has a canonical upstream archive and a SHA-256, is not in core or extra, and has been built at least once. Contribute with a GitHub pull request: one package, following CONTRIBUTING.md. CI indexes the tree against core and extra. A green check does not mean the package compiled; that is still your job.

Browse recipes on Splux Git and in the package list (filter: community). Clone from GitHub: github.com/RobertFlexx/sps-community.git.