Full Package Rebuild Toward SliTaz 5.1

June 2026

A major step for SliTaz. We are rebuilding every package in the cooking wok from scratch to produce a fresh, coherent stable release — SliTaz 5.1 — and returning the project to its proven Stable + Cooking development model.

Why Rebuild Everything

Years of rolling releases kept SliTaz current, but they left the package set uneven. Toolchains drifted over time, packages were built against different library versions at different moments, and reproducibility suffered. A full rebuild from a single, known toolchain gives us one clean, consistent baseline — every package compiled against the same libraries, with the same flags, on the same target. It is the only honest way to call a release stable.

Back to Stable + Cooking

SliTaz is returning to the development model that served it best: a frozen, polished Stable branch for users, and a Cooking branch where active development happens. Rolling was great for staying on the edge, but it blurred the line between "tested" and "in progress". With Stable + Cooking, users get a release they can trust and rely on, while contributors keep moving fast in Cooking without breaking anyone's system. Stable receives security and bug fixes; Cooking carries the new work that becomes the next stable.

Toward 5.1

The rebuild is underway. As packages are recompiled and validated, they flow into the Cooking branch. Once the full set is rebuilt, tested and frozen, it becomes SliTaz 5.1 stable. There is no firm date yet — it will be ready when it is solid, not before. We will share progress as milestones land.

Help Us Get There

This is a big effort, and the best kind of work to contribute to. You can help by:

Tools like TazLab let you build and cook SliTaz packages from any GNU/Linux host — no SliTaz install required. Come and talk to us on the forum — it is the best place to get involved.

— Christophe Lincoln (Pankso)