adding-a-package

To add a package to Bluefin, you create a BuildStream .bst element for your software, add it to the image's dependency list like deps.bst, and configure any required systemd services. This process ensures the new software is correctly built and integrated into the operating system image.

You can add packages built with Meson, CMake, Cargo, Make, autotools, Go, and Zig to Bluefin. The integration process supports adding pre-built binaries, compiling from source code, and including GNOME Shell extensions through dedicated BuildStream element creation.

Configuring systemd services in a merged-usr environment requires placing service and preset files in the correct directories. When adding packages to Bluefin, you must ensure these files are properly installed and defined within the BuildStream build elements to function correctly.

The best way to manage dependencies in Bluefin is to create BuildStream elements and add the new package to the image's dependency list. This approach ensures all required software components are correctly defined, built, and included in the final system image.

Adding a package to Bluefin fully supports pre-built binaries alongside source code compilation. You can create the necessary BuildStream elements to integrate pre-compiled software into the image without needing to build it from source.

You need to create a .bst file because BuildStream uses these elements to define how software is fetched, built, and integrated. Creating the file is the required step for adding any new command-line utility or package to the Bluefin image dependency list.