Packaging
The Garden Linux packaging system enables the creation of customized operating system images through a modular approach. This guide provides an overview of the complete package release lifecycle and links to detailed how-to guides for each stage.
Release Hierarchy
Garden Linux uses a three-tier release hierarchy to deliver a complete operating system.
This document is about the first tier, the Packaging Ecosystem.
Package Release Lifecycle
Creating and releasing packages in Garden Linux follows a structured process:
- Creating Packages: Start with this guide to learn how to create a new package or modify an existing one
- Applying Patches: Learn how to create and manage patches for both debian/ folder changes and upstream source modifications
- Building Packages: Choose your preferred method:
- Local Builds: Build packages on your development machine
- GitHub Actions: Automate builds with CI/CD
- Backporting: Create patch releases for specific Garden Linux versions
- Managing Dependencies: Handle special build-time dependencies with bp-package repositories
- Excluding Packages: Use NULL releases to temporarily exclude problematic packages from builds
Core Concepts
- Packaging Rules: Authoritative reference for all naming conventions and procedural rules
- Package Sources: Understand the different types of package sources in Garden Linux
- Repository Infrastructure: Learn how packages are assembled into apt repositories
Getting Started
- Review the Packaging Rules for naming conventions and repository structure
- Choose a package to work on (either a new package or modifying an existing one)
- Follow the Creating Packages guide to set up your package
- Use the appropriate build method (local or GitHub Actions)
- Test your package thoroughly before releasing
- Create a GitHub release to make it available for inclusion in Garden Linux
For maintainers creating packages for the first time, we recommend reading through all the guides in order to understand the complete workflow.