Haiku's Package Management System Goes Live
After a design drafted in January 2011 and development under funded contracts, Haiku's packagefs-based package management shipped in September 2013 — reshaping how software gets installed on the system.
Haiku’s modern package management system — built around packagefs, which mounts packages as a virtual file system rather than extracting them — went live in September 2013, after roughly two and a half years of design and implementation work.
From draft to funded project
The initial vision for how package management should work on Haiku was drafted in January 2011. The work needed to actually build it was substantial enough that it became a funded initiative, with contractors Ingo Weinhold and Oliver Tappe doing much of the core implementation — a notable example of Haiku’s development model combining volunteer contribution with paid, focused work on specific, well-scoped pieces of the system funded through the project’s nonprofit backing.
Why this was a bigger change than it sounds
Introducing packagefs meant fundamentally changing what /boot/system — the directory tree containing the core OS and its applications — actually is: not a normal directory tree at all, but a live merge of currently-activated packages, assembled and presented by packagefs on the fly. This is a deep architectural change to make to a running, actively-used operating system, not a surface-level addition, since a large amount of existing system software and tooling had assumptions about how the file system it lived in behaved.
A multi-year transition, not an overnight switch
Reaching a stable, well-integrated package management experience took considerably longer than the initial 2013 launch — the Haiku project’s own retrospectives describe the 2012–2016 period broadly as one of significant user-facing rough edges while the system and its surrounding tooling matured. Package management’s role as one of the headline features of Haiku’s first beta release, in 2018, reflects roughly how long it actually took from initial launch to a experience polished enough to anchor a major release.
Why this milestone mattered for Haiku’s long-term trajectory
A modern, coherent package management system was a prerequisite for Haiku to be taken seriously as an actively-developed, installable OS rather than a historical curiosity — reliable software installation and removal is a baseline expectation for any general-purpose system. Packagefs going live in 2013 was the point where that baseline capability, engineered specifically to fit Haiku’s own architecture rather than importing another platform’s approach wholesale, actually started being built in earnest.
Sources: Package Management for Haiku — Haiku Project blog, A brief summary of Haiku’s package management — Haiku Project blog, Package Management Infrastructure — Haiku internals documentation