Patching Unpatchable Files

In the Yocto world, the .bbappend file is a well-known and documented mechanism for altering recipe files, and an essential part of daily operations. While not common, there are instances where it becomes necessary to modify other file types, such as .inc or .bbclass, which do not offer an equivalent append mechanism. This session will summarize various strategies for effectively handling these file types when patching cannot be avoided.

In my recent presentation at the Yocto Developer Day in Vienna, I mentioned using the KAS patch mechanism for minor modifications to files like .inc or .bbclass, where the Yocto internal overwriting mechanism via .bbappend files does not apply. Initially intended as a helpful side note on how I navigated a few unique situations, this part quickly escalated into the most discussed segment of the talk. Half of the attendees I spoke with found it valuable, while the other half expressed strong objections.

In this follow-up session, I aim to dive deeper into the complexities of working with these “unpatchable” files and explore the following key questions:

In which situations is patching valid? What strategies and approaches —both well-known and lesser-known— are generally available? Which strategy is best suited for different scenarios and use cases? In conclusion, this talk aims to present and document various strategies for addressing the challenge of “patching unpatchable files” and to encourage discussions on best practices.

Presented at

• Yocto Project Summit 2024.12, virtual