Development process

• Follow upstream development of CRUX
• Review TODO, Changelog and issues from CRUX
• Review issues at:
  • crux-rootfs repository (You need to signIn or register to check the repository)
• Review issues at:
  • core-arm and core-arm64 ports collections at Gitea (You need to signIn or register to check the repository)
  • core-arm and core-arm64 ports collections at Github
• Prepare new branches in main repositories (those mentioned in the previous point) with new ports versions and differences
• Start the bootstrap process for aarch64 (dockerized version). For a more detailed explanation, you can check this README.md
  • Prepare Stage:
    • Creates a directory structure for logs and checks out a current copy of port repositories from the CRUX/CRUX-ARM project.
  • Stage 0:
    • It will build the necessary base packages from upstream CRUX/CRUX-ARM repositories for the selected architecture.
    • These packages are installed in the rootfs-stage0 directory.
  • Stage 1:
    • Using the packages from Stage 0, the system is chrooted into a fresh environment (rootfs-chroot-stage1) to rebuild the complete core collection.
    • These packages are installed in the rootfs-stage1 directory.
  • Release Creation:
    • The contents of rootfs-stage1 are packaged into a compressed archive (e.g. crux[-arm]-VERSION.rootfs.tar.xz) to create the final release rootfs.
  • Additional files:
    • an importable LXC/LXD image
    • an OCI image
• Repeat the process for armhf architecture
• Repeat the process for all optimizations for both architectures
• Open the contribute window for other users who wants to add another devices support. Check how to do it:
  • How to contribute
• Schedule CI pipe to rebuild updated release automatically, publish it at gitea and upload OC image to gitea's registry