adding-a-package

Create BuildStream elements and configure systemd services for Bluefin packages.

134|27|Updated Nov 16, 2025

Search Tags:#dependency management #packaging #software #systemd #buildstream #bluefin

Ready to run

npx skills add https://github.com/projectbluefin/dakota --skill adding-a-package

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adding-a-package
Source: https://github.com/projectbluefin/dakota/tree/main/.opencode/skills/adding-a-package
Command: npx skills add https://github.com/projectbluefin/dakota --skill adding-a-package

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of integrating new software packages into the Bluefin operating system image, ensuring they are correctly defined, built, and included.

Core Features & Use Cases

Package Integration: Guides users through creating BuildStream elements for various software types (binaries, source code with different build systems, config files).
Dependency Management: Explains how to add new packages to the image's dependency list.
Systemd Service Setup: Details the correct placement and configuration for systemd service and preset files in a merged-usr environment.
Use Case: A developer needs to add a new command-line utility to the Bluefin image. They use this Skill to create the necessary .bst file, add it to deps.bst, and ensure the service file is correctly installed.

Quick Start

Use the adding-a-package skill to add a new package to the bluefin-egg BuildStream build.

Frequently Asked Questions about adding-a-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add a new package to a Bluefin build using BuildStream?▼

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.

Can I add packages built with Meson, CMake, or Cargo to Bluefin?▼

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.

How do I configure systemd services when adding packages to a merged-usr environment?▼

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.

What is the best way to manage dependencies when integrating software into an OS image?▼

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.

Does adding a package to Bluefin support pre-built binaries?▼

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.

Why do I need to create a .bst file for Bluefin package integration?▼

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.