Template files and build system (public logs available) for https://static.itmodulo.eu/dl/repo/alpine
Go to file
ITmodulo 393a1c1c06
Release Alpine apk for ARM64v8 / compilation-arm64v8 (push) Waiting to run Details
Update hunspell checksum
2024-02-22 22:11:17 +01:00
.gitea/workflows Update hunspell 2024-02-22 22:09:01 +01:00
srcpkgs Update hunspell checksum 2024-02-22 22:11:17 +01:00
LICENSE Initial commit 2024-01-27 16:08:26 +01:00
README.md Fix libsearpc add subpackage -pyc 2024-01-31 12:12:06 +01:00

README.md

Public custom Alpine Linux repo

Template files and build system (public logs available) for https://static.itmodulo.eu/dl/repo/alpine

Disclaimer

  1. Don't use this repo if you don't know what you are doing. It may break your great Alpine Linux experience
  2. If you want to upstream, go ahead but don't engage me -> You maintain. Although You are allowed reference as working example without restrictions.
  3. Builds here will be only musl-aarch64 for now, altough I may consider other variants if you donate me every month
  4. Maintained in mind with postmarketOS and Alpine latest-stable
  5. I may rename/remove package without prior notification.

Why

To maintain own repo

Official repo is good quality however:

  • It simply lacks some packages I need.
  • Some packages are in testing linked against newer versions od their dependencies. Instead of adding from testing I would prefer to bake them myself
  • I don't use flatpak for personal reason (mostly size of packages and sdks based mostly on sth like EOL ubuntu I don't really like)
  • Instead flatpaks I would use AppImages that are not so easy to update in large quantity moreover they don't work on Alpine as linked against glibc

To use repo actions for builds

  • It's easy to maintain
  • Public build logs are more trustworthy (for potential other users)
  • Clear and simple repo structure

Builds

  • Built on docker with actions on this repo
  • Signed with private key
  • Triggered on push to release branch
  • Release branch always compile
  • New packages tested on other branches

LICENSE

Actions workflow file and template files are licensed under BSD-3-Clause-no-military

This should not impact the original source code licenses