Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/gbrlsnchs/my-aports

My custom aports definitions for Alpine Linux
https://github.com/gbrlsnchs/my-aports

alpine-linux aports custom-package

Last synced: 10 days ago
JSON representation

My custom aports definitions for Alpine Linux

Awesome Lists containing this project

README

        

# My aports
## About
These are my custom aports for my private aports repository at https://aports.gsr.dev.

## How to use
### Public key
Download public keys from https://aports.gsr.dev/keys and place them at `/etc/apk/keys/`.
### Repository Add the repository to the repository list. I prefer using a tag for it:

```console
echo "@custom https://aports.gsr.dev/repositories/main" >> /etc/apk/repositories
```

Then, it's possible to install a package from it, for example,
[Park](https://codeberg.org/gbrlsnchs/park):
```console
apk add park@custom
```

### Building packages
#### Cross-compilation
It's possible to cross-compile packages with [`qemu-user-static`](https://github.com/multiarch/qemu-user-static).

#### Dependencies
##### x86_64 only
- `podman`
##### Cross-compilation (aarch64)
- `qemu`
- `qemu-user-static`
- `binfmt-support`

#### Steps
If it's the first time using the repository, build the base container image and then generate a key
pair:
```console
./scripts/mkimg
./scripts/keygen
```
Then, for every package you want to build (considering you already have the appropriate template and
necesary files):
1. `./scripts/lint path/to/package` (optional)
2. `./scripts/checksum path/to/package`
3. `./scripts/build path/to/package`
4. `./scripts/index`
5. `./scripts/sign`
6. `./scripts/mkpages`