Build pipelines for c10y BSD packages
- Makefile 74.9%
- Shell 25.1%
|
All checks were successful
Build FreeBSD package / build (generic, 15) (push) Successful in 24m35s
Build FreeBSD package / build (generic, 14) (push) Successful in 28m54s
Build FreeBSD package / build (haswell, 15) (push) Successful in 23m18s
Build OpenBSD package / build (generic) (push) Successful in 51m23s
Build FreeBSD package / build (haswell, 14) (push) Successful in 24m47s
Build OpenBSD package / build (haswell) (push) Successful in 48m18s
|
||
|---|---|---|
| .forgejo/workflows | ||
| freebsd | ||
| openbsd | ||
| README.md | ||
continuwuity-bsd
Build tools for releasing BSD packages for the continuwuity Matrix homeserver.
Why aren't these in the ports trees?
The build process for Continuwuity conflicts with the package build infrastructure. Package builds cannot have network access during the build stage, and Cargo downloads crates and Git repositories during build. Build mechanisms which attempt to download dependencies ahead of time appear to be incompatible with Continuwuity's forked crates, such as async-channel and core_affinity.