PorkAlpine Package Repositories

PorkAlpine depends upon upstream Alpine, and adds its own repo. Where possible, packages may be upstreamed to normal Alpine eventually, but there may be packages specific to hotspots, repeaters, and similar that upstream Alpine would not want.

If you installed from an iso or the Raspberry Pi disk images, then you’re already set.

If you want to use any of the PorkAlpine packages on a standard Alpine installation, you must both

import the package signing key(s) and
add the package repositories

After that, you can apk update and start installing packages.

Instructions for exactly those steps follow.

Package Signing Key

The contents of the public keys of the PorkAlpine maintainers must be in a file each in /etc/apk/keys. There is currently only one key.

Warning: You are trusting the owners of these keys to publish software that runs on your Alpine-running device.

Only do this if you understand the implications, from security through reliability (in short, you are giving a lot of trust to the owner of the private key - that’s me).

/etc/apk/keys/alpine\@tarxvf.tech-6207feba.rsa.pub

Add package repository

Add the following line to /etc/apk/repositories, which should already have some package mirrors:

https://repo.porkalpine.org/v3.20/

This means you might have a file like:

https://dl-cdn.alpinelinux.org/alpine/v3.20/main
https://dl-cdn.alpinelinux.org/alpine/v3.20/community
https://repo.porkalpine.org/v3.20/

At the time of writing in February 2025, Alpine 3.20 is the only supported version. PorkAlpine is expected to follow upstream Alpine, so the version number may change in the future.

Note that the repo host does not have indexes turned on, so don’t be alarmed by the blank page if you load it up in a web browser.

An RSS feed and mailing list will be published with critical news once that’s needed. In the meantime, watch this website.

PorkAlpine Package Repositories

Tue Feb 4, 2025

Package Signing Key

Add package repository