packaging-gnome-shell-extensions

Package GNOME Shell extensions in BuildStream with Meson or Make patterns.

134|27|Updated Nov 16, 2025

Search Tags:#packaging #extensions #makefile #meson #gsettings #buildstream #gnome shell

Ready to run

npx skills add https://github.com/projectbluefin/dakota --skill packaging-gnome-shell-extensions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: packaging-gnome-shell-extensions
Source: https://github.com/projectbluefin/dakota/tree/main/.opencode/skills/packaging-gnome-shell-extensions
Command: npx skills add https://github.com/projectbluefin/dakota --skill packaging-gnome-shell-extensions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of packaging GNOME Shell extensions for BuildStream, ensuring they are correctly integrated into the system image and function as expected.

Core Features & Use Cases

Extension Packaging: Provides patterns for packaging extensions based on their build systems (Meson, Make, Manual).
UUID Handling: Manages the extraction and correct placement of extension UUIDs.
Schema Compilation: Ensures GSettings schemas are correctly compiled and integrated.
Use Case: When adding a new GNOME Shell extension to the Bluefin OS image, use this Skill to determine the correct BuildStream element definition based on the extension's build system and dependencies.

Quick Start

Use the packaging-gnome-shell-extensions skill to define a BuildStream element for a GNOME Shell extension that uses a Makefile and needs UUID extraction.

Frequently Asked Questions about packaging-gnome-shell-extensions

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

FAQPage Schema

How do I package GNOME Shell extensions using BuildStream?▼

Packaging GNOME Shell extensions with BuildStream involves defining a BuildStream element that matches the extension's build system, such as Meson or Make. This ensures correct integration into the system image by handling UUID extraction and schema compilation.

How does GSettings schema compilation work for GNOME Shell extensions?▼

GSettings schema compilation for GNOME Shell extensions ensures schemas are correctly compiled and integrated into the environment. This process handles schema relocation and compilation during the BuildStream packaging step to ensure seamless extension functionality.

Can I use Meson to build GNOME Shell extensions in BuildStream?▼

Yes, you can use Meson to build GNOME Shell extensions in BuildStream. This approach provides specific packaging patterns for Meson-based extensions, alongside Makefile and manual configurations, ensuring proper system integration and functionality.

What is the best way to handle UUID extraction for GNOME Shell extensions?▼

The best way to handle UUID extraction for GNOME Shell extensions is by utilizing the build patterns provided for Make and manual packaging. This manages the extraction and correct placement of extension UUIDs within the BuildStream build system.

Why does my GNOME Shell extension binary fail after packaging?▼

Your GNOME Shell extension binary might fail after packaging due to improper binary stripping or incorrect GSettings schema compilation. Addressing these common issues during the BuildStream packaging process ensures seamless integration into the GNOME Shell environment.