[Buildroot] customizations to package recipes in BR2_EXTERNAL?
casantos at datacom.com.br
Mon Jun 18 11:48:44 UTC 2018
> From: "Liam Staskawicz" <liam at stask.net>
> To: "buildroot" <buildroot at busybox.net>
> Sent: Sunday, June 17, 2018 6:30:14 PM
> Subject: [Buildroot] customizations to package recipes in BR2_EXTERNAL?
> I'd like to slightly modify an existing package (nvidia-driver) to target a
> different version (not the latest version, just the specific version my project
> is using). The changes are simple - updating the version string, and .hash
> entries - but it's not clear how best to manage these changes in a BR2_EXTERNAL
> based workflow, as patches in BR2_GLOBAL_PATCH_DIR get applied after the
> sources have been downloaded and unpacked.
> I'd like to avoid maintaining a clone of the buildroot repo with these changes,
> if possible. Is there a recommended workflow for this situation?
Allowing users to customize existing packages in a BR2_EXTERNAL could
lead to unpredictable results. If you need a custom nvidia-driver then
copy/edit the original package definition to <my-project>-nvidia-driver
in your BR2_EXTERNAL. That's quite easy, since no other package depends
A more generic solution would be allowing the user to select the desired
version by means of a sub-menu. This seems to make sense for a package
that install pre-compiled binaries, like nvidia-driver does.
Let's ask the opinion of the package maintainers (in CC).
Carlos Santos (Casantos) - DATACOM, P&D
“Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.” — Epitaph of a volunteer
More information about the buildroot