[$] Bootstrappable builds: how and why
This year's edition of the Free and Open Source Software Yearly conference , better known as "FOSSY", moved north to the beautiful (and enormous) campus of the University of British Columbia (UBC) in Vancouver, Canada from its home for the three previous editions: Portland, Oregon, in the US. There were many different types of talks at FOSSY, from deeply technical kernel-track topics, through…
The Free and Open Source Software Yearly conference, dubbed FOSSY, recently relocated to the expansive University of British Columbia (UBC) campus in Vancouver, Canada. This marked a shift from its three previous editions held in Portland, Oregon, within the United States.
FOSSY featured a diverse range of discussions, spanning technical kernel-track topics, legal and community issues, and the practical application of FOSS in daily life. Among these talks, a presentation on bootstrappable builds took center stage within the "Toolchains and Other Development Tools" track.
Timothy Sample, the presenter, delved into the concept of bootstrappable builds, a topic that, while related to its more well-known counterpart, reproducible builds, remains less widely recognized. Reproducible builds, as briefly covered by LWN over two years ago, involve creating code with a thoroughly understood origin.
In essence, a bootstrappable build commences with an extremely minimal program capable of constructing a marginally larger program. This process continues, incrementally building larger programs from smaller ones, until a comprehensive Linux user space is assembled from a mere seed. The result is code that can be traced back to its original source, a stark contrast to the typical Linux user space of today.
Written by urgent.news from LWN's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.