Resolve naming conflicts

Author: binarypie

Containerfile

@@ -5,14 +5,40 @@ ARG BASE_IMAGE=ghcr.io/ublue-os/bluefin-dx:stable-daily
 FROM scratch AS ctx
 COPY build_files /
 
+# Build Elephant from source (cached layer)
+FROM ${BASE_IMAGE} AS elephant-builder
+COPY packages/elephant/build.sh /tmp/build-elephant.sh
+RUN --mount=type=cache,dst=/var/cache \
+  --mount=type=cache,dst=/var/log \
+  --mount=type=tmpfs,dst=/tmp/build \
+  chmod +x /tmp/build-elephant.sh && \
+  /tmp/build-elephant.sh
+
+# Build Walker from source (cached layer)
+FROM ${BASE_IMAGE} AS walker-builder
+COPY packages/walker/build.sh /tmp/build-walker.sh
+RUN --mount=type=cache,dst=/var/cache \
+  --mount=type=cache,dst=/var/log \
+  --mount=type=tmpfs,dst=/tmp/build \
+  chmod +x /tmp/build-walker.sh && \
+  /tmp/build-walker.sh
+
 # Base Image
 FROM ${BASE_IMAGE}
 
-# Copy dot_files into the image at /usr/share/binaryos/config
-COPY dot_files /usr/share/binaryos/config
+# Copy Elephant binary and service from builder
+COPY --from=elephant-builder /usr/bin/elephant /usr/bin/elephant
+COPY --from=elephant-builder /usr/lib/systemd/user/elephant.service /usr/lib/systemd/user/elephant.service
+
+# Copy Walker binary and resources from builder
+COPY --from=walker-builder /usr/bin/walker /usr/bin/walker
+COPY --from=walker-builder /usr/share/walker /usr/share/walker
+
+# Copy dot_files into the image at /usr/share/hypercube/config
+COPY dot_files /usr/share/hypercube/config
 
 # Ensure all config files are readable by everyone
-RUN chmod -R a+rX /usr/share/binaryos/config
+RUN chmod -R a+rX /usr/share/hypercube/config
 
 ## Other possible base images include:
 # FROM ghcr.io/ublue-os/bazzite:latest

Justfile

@@ -83,8 +83,8 @@ sudoif command *args:
 # just build $target_image $tag $base_img
 #
 # Example usage:
-#   just build binaryos latest
-#   just build binaryos nvidia ghcr.io/ublue-os/bluefin-dx-nvidia:stable-daily
+#   just build hypercube latest
+#   just build hypercube nvidia ghcr.io/ublue-os/bluefin-dx-nvidia:stable-daily
 #
 # This will build an image with the specified base image.
 #

README.md

@@ -1,18 +1,18 @@
-# BinaryOS
+# Hypercube
 
-BinaryOS is a custom [bootc](https://github.com/bootc-dev/bootc) image built on top of [Bluefin-DX](https://projectbluefin.io/) with Hyprland and an opinionated set of development tools. This image is designed primarily for my personal software development workflow, but you're welcome to use it, fork it, or submit issues and pull requests.
+Hypercube is a custom [bootc](https://github.com/bootc-dev/bootc) image built on top of [Bluefin-DX](https://projectbluefin.io/) with Hyprland and an opinionated set of development tools. This image is designed primarily for my personal software development workflow, but you're welcome to use it, fork it, or submit issues and pull requests.
 
 ## What's Inside
 
-BinaryOS builds on Bluefin-DX's excellent developer experience foundation and adds:
+Hypercube builds on Bluefin-DX's excellent developer experience foundation and adds:
 
 - **Hyprland**: A dynamic tiling Wayland compositor for an efficient, keyboard-driven workflow
 - **Opinionated Development Tools**: A curated set of tools and configurations optimized for my development workflow
 - **Personal Preferences**: Custom configurations and tweaks that I've found useful over time
 
 ### Available Variants
 
-BinaryOS is available in two variants:
+Hypercube is available in two variants:
 
 - **Regular**: Built on `bluefin-dx:stable-daily` for systems with Intel/AMD graphics
 - **NVIDIA**: Built on `bluefin-dx-nvidia:stable-daily` with NVIDIA driver support
@@ -37,18 +37,18 @@ While this is a personal image, community contributions are welcome! If you enco
 - A machine running a bootc-compatible image (e.g., Bazzite, Bluefin, Aurora, or Fedora Atomic)
 - Basic familiarity with bootc and container-based operating systems
 
-### Switching to BinaryOS
+### Switching to Hypercube
 
 From your existing bootc system, run:
 
 **For systems with Intel/AMD graphics:**
 ```bash
-sudo bootc switch ghcr.io/binarypie/binaryos:latest
+sudo bootc switch ghcr.io/binarypie-dev/hypercube:latest
 ```
 
 **For systems with NVIDIA graphics:**
 ```bash
-sudo bootc switch ghcr.io/binarypie/binaryos:latest-nvidia
+sudo bootc switch ghcr.io/binarypie-dev/hypercube:latest-nvidia
 ```
 
 Then reboot your system:
@@ -57,11 +57,11 @@ Then reboot your system:
 systemctl reboot
 ```
 
-After rebooting, you'll be running BinaryOS.
+After rebooting, you'll be running Hypercube.
 
 ### Switching Back
 
-If BinaryOS isn't for you, you can switch back to your previous image:
+If Hypercube isn't for you, you can switch back to your previous image:
 
 ```bash
 sudo bootc status  # Find your previous image
@@ -71,7 +71,7 @@ systemctl reboot
 
 ## Customization & Forking
 
-Want to create your own variant of BinaryOS? You're welcome to fork this repository! Here's how the build system works:
+Want to create your own variant of Hypercube? You're welcome to fork this repository! Here's how the build system works:
 
 ### Repository Structure
 
@@ -94,7 +94,7 @@ For detailed information about customizing the image, see the files mentioned ab
 
 The repository includes workflows for creating bootable disk images (ISO, QCOW2, raw) using [bootc-image-builder](https://osbuild.org/docs/bootc/). These can be used for:
 
-- Installing BinaryOS on bare metal (ISO)
+- Installing Hypercube on bare metal (ISO)
 - Testing in virtual machines (QCOW2)
 - Deploying to cloud environments (raw)
 
@@ -108,23 +108,23 @@ You can also build disk images locally using the included `just` commands (see [
 
 ## Artifacthub
 
-BinaryOS is indexed on [artifacthub.io](https://artifacthub.io) to make it easier to discover and track. If you fork this image, you can list your own variant there as well using the `artifacthub-repo.yml` file.
+Hypercube is indexed on [artifacthub.io](https://artifacthub.io) to make it easier to discover and track. If you fork this image, you can list your own variant there as well using the `artifacthub-repo.yml` file.
 
 Learn more in the [Universal Blue Artifacthub discussion](https://universal-blue.discourse.group/t/listing-your-custom-image-on-artifacthub/6446).
 
 ## Development with Just
 
-The repository includes a [`Justfile`](./Justfile) with commands for building and testing BinaryOS locally. [just](https://just.systems/) is a command runner that simplifies common development tasks.
+The repository includes a [`Justfile`](./Justfile) with commands for building and testing Hypercube locally. [just](https://just.systems/) is a command runner that simplifies common development tasks.
 
-Just is pre-installed on all Universal Blue images (including BinaryOS and Bluefin-DX). If you're using another system, install it from your package manager or see the [just installation guide](https://just.systems/man/en/introduction.html).
+Just is pre-installed on all Universal Blue images (including Hypercube and Bluefin-DX). If you're using another system, install it from your package manager or see the [just installation guide](https://just.systems/man/en/introduction.html).
 
 ### Available Commands
 
 Run `just` without arguments to see all available commands. Here are the most useful ones:
 
 #### Building
 
-- `just build` - Build the BinaryOS container image locally (regular variant)
+- `just build` - Build the Hypercube container image locally (regular variant)
 - `just build-regular` - Build the regular variant (Intel/AMD graphics)
 - `just build-nvidia` - Build the NVIDIA variant
 - `just build-all` - Build both regular and NVIDIA variants
@@ -134,8 +134,8 @@ Run `just` without arguments to see all available commands. Here are the most us
 
 #### Testing
 
-- `just run-vm-qcow2` - Run BinaryOS in a VM using QCOW2 image
-- `just spawn-vm` - Run BinaryOS using systemd-vmspawn
+- `just run-vm-qcow2` - Run Hypercube in a VM using QCOW2 image
+- `just spawn-vm` - Run Hypercube using systemd-vmspawn
 
 #### Maintenance
 
@@ -147,9 +147,9 @@ For detailed usage and additional commands, see the [Justfile](./Justfile) itsel
 
 ## Related Projects
 
-BinaryOS is part of the larger Universal Blue ecosystem. Check out these other custom images for inspiration:
+Hypercube is part of the larger Universal Blue ecosystem. Check out these other custom images for inspiration:
 
-- [Bluefin-DX](https://projectbluefin.io/) - The base image for BinaryOS
+- [Bluefin-DX](https://projectbluefin.io/) - The base image for Hypercube
 - [m2Giles' OS](https://github.com/m2giles/m2os) - Another custom bootc image
 - [bOS](https://github.com/bsherman/bos) - Custom image by bsherman
 - [Homer](https://github.com/bketelsen/homer/) - Custom image by bketelsen
@@ -162,7 +162,7 @@ This project follows the same licensing as the Universal Blue project. See the L
 
 ## Acknowledgments
 
-BinaryOS is built on the shoulders of giants:
+Hypercube is built on the shoulders of giants:
 
 - [Universal Blue](https://universal-blue.org/) for the excellent image-based desktop platform
 - [Project Bluefin](https://projectbluefin.io/) for the outstanding developer experience foundation

artifacthub-repo.yml

@@ -2,7 +2,7 @@
 # Sign up and add the Repository ID to the right field. Owners fields are optional.
 # Examples: https://artifacthub.io/packages/search?ts_query_web=ublue&sort=relevance&page=1
 
-repositoryID: binarypie/binaryos
+repositoryID: binarypie-dev/hypercube
 owners:
   - name: binarypie
     email: [email protected]

build_files/60-binaryos-xdg.conf

@@ -0,0 +1,18 @@
+# Hypercube XDG Configuration
+#
+# This configuration adds Hypercube system configs to the XDG search paths.
+#
+# Config lookup order (highest to lowest priority):
+#   1. ~/.config/          - User overrides
+#   2. /etc/xdg/           - Admin overrides
+#   3. /usr/share/hypercube/config/ - Hypercube defaults (always current)
+#
+# Data lookup order:
+#   1. ~/.local/share/     - User data
+#   2. /usr/local/share/   - Local admin data
+#   3. /usr/share/         - System data
+#   4. /usr/share/hypercube/data/ - Hypercube data
+
+XDG_CONFIG_DIRS=/etc/xdg:/usr/share/hypercube/config
+XDG_DATA_DIRS=/usr/local/share:/usr/share:/usr/share/hypercube/data
+

build_files/60-hypercube-xdg.conf

@@ -133,19 +133,19 @@ dnf5 -y install neovim python3-neovim
 
 # Fish shell configs
 # Fish doesn't use XDG_CONFIG_DIRS, so we install to /etc/fish
-install -Dm644 /usr/share/binaryos/config/fish/config.fish /etc/fish/config.fish
-cp -r /usr/share/binaryos/config/fish/conf.d /etc/fish/
-cp -r /usr/share/binaryos/config/fish/functions /etc/fish/ 2>/dev/null || true
-cp -r /usr/share/binaryos/config/fish/completions /etc/fish/ 2>/dev/null || true
+install -Dm644 /usr/share/hypercube/config/fish/config.fish /etc/fish/config.fish
+cp -r /usr/share/hypercube/config/fish/conf.d /etc/fish/
+cp -r /usr/share/hypercube/config/fish/functions /etc/fish/ 2>/dev/null || true
+cp -r /usr/share/hypercube/config/fish/completions /etc/fish/ 2>/dev/null || true
 
 # Wezterm configs
 # Wezterm doesn't support XDG_CONFIG_DIRS for system defaults, so we install to /etc/skel
 # which will be copied to new user home directories
-install -Dm644 /usr/share/binaryos/config/wezterm/wezterm.lua /etc/skel/.config/wezterm/wezterm.lua
+install -Dm644 /usr/share/hypercube/config/wezterm/wezterm.lua /etc/skel/.config/wezterm/wezterm.lua
 
-# Configure XDG environment for BinaryOS
-# This makes all configs in /usr/share/binaryos/config discoverable
+# Configure XDG environment for Hypercube
+# This makes all configs in /usr/share/hypercube/config discoverable
 # while preserving user and admin override capabilities
-install -Dm644 /ctx/60-binaryos-xdg.conf /usr/lib/environment.d/60-binaryos-xdg.conf
+install -Dm644 /ctx/60-hypercube-xdg.conf /usr/lib/environment.d/60-hypercube-xdg.conf
 
 # systemctl enable podman.socket

build_files/build.sh

@@ -1,4 +1,4 @@
-# Elephant Configuration - BinaryOS
+# Elephant Configuration - Hypercube
 # Configuration for the Elephant data provider service
 
 # Disable Arch Linux packages provider since we're on Fedora

dot_files/elephant/elephant.toml

@@ -59,13 +59,13 @@ exec-once = walker --gapplication-service
 exec-once = systemctl --global start mako.service
 
 # Wallpaper
-exec-once = hyprpaper -c /usr/share/binaryos/config/hypr/hyprpaper.conf
+exec-once = hyprpaper -c /usr/share/hypercube/config/hypr/hyprpaper.conf
 
 # OSD
 exec-once = swayosd-server
 
 # Idle / Lock
-exec-once = hypridle -c /usr/share/binaryos/config/hypr/hypridle.conf
+exec-once = hypridle -c /usr/share/hypercube/config/hypr/hypridle.conf
 
 # GNOME Polkit Authentication Agent (for privilege escalation)
 exec-once = /usr/libexec/polkit-gnome-authentication-agent-1

dot_files/hypr/hyprland.conf

@@ -11,7 +11,7 @@ general {
 # Replace the path below with your custom wallpaper
 background {
     monitor =
-    path = /usr/share/binaryos/config/hypr/background.webp  # Change this to your image path
+    path = /usr/share/hypercube/config/hypr/background.webp  # Change this to your image path
     blur_passes = 3
     blur_size = 7
     noise = 0.0117