ECZOS

ECZOS is an EasyComp Zeeland operating-system product layer built on Debian. The current development baseline is Debian 13 (Trixie), KDE Plasma 6 and SDDM.

The project is not a fork of Debian and must not replace Debian-owned files for branding alone. ECZOS-specific behaviour is delivered through versioned Debian packages, declarative profiles and a reproducible image configuration.

Download ECZOS 0.1.1

• Official ECZOS website
• Download ECZOS 0.1.1 for amd64
• SHA-256 checksum
• ECZOS software repository

The installation image supports BIOS and UEFI systems and can be written to a USB drive, SD card or other installation medium with ECZOS Recovery Media Creator or another image-writing tool.

Current status

ECZOS 0.1.1 is the current stable maintenance release. This repository contains the complete source for the ECZOS product layer, native tools, installer presentation, first-start experience, desktop integration and reproducible image pipeline. Historical machine snapshots and experimental builds remain outside Git.

Layout

docs/                       Architecture, decisions, security and roadmap
packages/eczos-branding/    First Debian source package
packages/eczos-sddm-theme/  ECZOS login theme and SDDM configuration
packages/eczos-plymouth-theme/ ECZOS boot-splash theme
packages/eczos-desktop-defaults/ One-time Plasma appearance defaults
packages/eczos-release/       Product identity without masking Debian
packages/eczos-windows-core/  Managed EXE/MSI compatibility MVP
packages/eczos-gaming-core/   Vulkan and UMU/Proton readiness gate
packages/eczos-platform-tools/ Control center, migration and diagnostics
packages/eczos-desktop-apps/  Supported native application metapackage
packages/eczos-desktop/       Complete desktop product-layer metapackage
scripts/                    Source-tree developer checks
tests/                      Automated source and package tests
image/                      Versioned Debian live-build configuration

The directories Build/, Assets/ and easycomp-desktop/ predate this source layout. Build/ and the old machine overlay are not source and are ignored. Canonical assets are copied into their owning package.

Development

Run the source checks on any Unix-like development machine:

./scripts/verify-source.sh

Run the package lifecycle tests on the dedicated Debian 13 test host:

sudo ./scripts/test-branding-package-vm.sh
sudo ./scripts/test-sddm-theme-package-vm.sh
sudo ./scripts/test-plymouth-theme-package-vm.sh
sudo ./scripts/test-desktop-defaults-package-vm.sh

The current combined product gate is run on that host with:

sudo ./scripts/install-next-product-batch-vm.sh

It installs FreeOffice from the signed SoftMaker repository and tests the ECZ Windows MSI, extracted-icon, repair and removal lifecycle before producing a visible-branding audit.

No production image should include the historical remote-support package. See docs/security.md.

Build a reviewed image on Debian 13 with:

sudo ./scripts/build-image-vm.sh

GitHub release upload directory

The allowlisted files for the latest GitHub release are generated in Build/GitHub/UPLOAD-THIS-TO-GITHUB/. Refresh the directory manually with:

make github-upload

This checkout also uses tracked Git hooks to refresh the directory after every commit, branch checkout and merge. Only the release notes, checksum and upload instructions are copied. ISO images, credentials, signing keys and build caches are deliberately excluded.

The complete source repository intended for GitHub Desktop is maintained separately in Build/GitHub/ECZOS-SOURCE/. It is a clean Git clone containing only committed project files and history. Untracked share content such as the separate website/ project, ISO images, credentials and build output cannot be copied into it. Refresh it manually with:

make github-source