You are browsing as a guest. Sign up (or log in) to start making projects!

chiron_dev8

@chiron_dev8

Joined June 5th, 2026

  • 3Devlogs
  • 2Projects
  • 2Ships
  • 15Votes
Ship Changes requested

@chiron_dev8 on centaur

I have worked on the project for a while before Stardance started. Probably around 95% of my hours are unlogged.

I have made a package manager for UNIX based systems (specifically for my custom Linux based operating system, ChironOS). It can install, uninstall and update packages, manage dependencies, sync install files to the latest versions and automatically remove all unused packages. My favourite part of the project was finally seeing all the functions working together.

I will still be working on this for a long long time as there is a lot I can improve on. My next goal will be to make package scripts for the whole of Linux From Scratch and Beyond LFS as this will prove the reliability of my package manager.

If you want to test this please make sure you are using Linux (It will probably work on BSD but I haven't tested it. It probably won't work on mac and it DEFINITELY WILL NOT WORK ON WINDOWS). Make sure to read the wiki for installation and usage instructions.

peace

  • 2 devlogs
  • 4h
Try project → See source code →
Open comments for this post

@chiron_dev8 on centaur

3h 54m 20s logged

Centaur v1.1 Release Notes

In this release, I focused on improving the .centaur package format and fixing several usability issues from v1.0.

What I changed

1. I redesigned the .centaur syntax into 3 clear sections

I changed .centaur files so package data is now split into:

  • [meta]
  • [install]
  • [uninstall]

This replaces the old mixed format where metadata, install steps, and uninstall script generation were all blended together.

2. I made metadata explicit and easier to parse

In v1.0, package metadata and dependency handling relied on ad-hoc placement (for example, dependency lines and markers like === ADD DEPENDENCIES ABOVE THIS LINE ===).

In v1.1, I moved this into a structured metadata block, for example:

  • name = "writedoc"
  • version = "2.3-p1"
  • dependencies = "example"

This makes package definitions cleaner and far more consistent.

3. I separated install and uninstall logic

I moved installation commands into [install] and uninstall commands into [uninstall].

Previously, uninstall behavior was created indirectly during install by writing uninstall commands into another file.
Now I define uninstall behavior directly in the package script itself, which is simpler and easier to maintain.

4. I fixed parser/runtime snags from v1.0

I resolved several pain points in .centaur files, including:

  • line length limit issues
  • newline/formatting sensitivity (such as needing blank lines between commands)
  • general script parsing/execution reliability issues

Result

With v1.1, I made .centaur scripts more structured, more readable, and more reliable.
The new format is easier for me (and others) to write, maintain, and parse going forward.

0
0
1
Ship Pending review

@chiron_dev8 on LitePad

**LitePad!**

LitePad is a 6 key, 2x3 keypad with a rotary encoder, OLED display and an RGB LED using QMK firmware. The aim for this project is to create a simple macropad to control govee smart LED bulbs via a host PC!

Features:

Awesome case!
128x32 OLED Display
EC11 Rotary Encoder
1 WS2812B RGB LED
6 Keys

CAD Model:

Uses 4 M3 Screws to hold the two parts of the case together. The PCB is placed inside the case with a cutout for every component and USB port. Designed in Autodesk Fusion in a Windows 11 VM (I use gentoo linux but I hate FreeCAD)

Firmware:

Currently unfinished as I am new to QMK. I will soon add features to communicate with a host PC with serial which will then control the govee lights. Currently it sits around and does nothing.

What you need to make this keypad thingy:

6x Cherry MX switches
6x DSA Keycaps
4x M3 16mm bolts
6x 1N4148 Diodes
1x WS2812B LED
1x 0.91" 128x32 OLED Display
1x EC11 Rotary Encoder
1x XIAO RP2040
1x Case (1x Bottom part, 1x Top part)
Some love <3

Extras:

Thank you to Hack Club for being awesome and supporting me :) (Also I need work experience...)

Video of Project → See source code →
Open comments for this post

@chiron_dev8 on centaur

17m 3s logged

I’m currently working on improving how I go about parsing package metadata. Previously, package dependencies were declared at the top of the file, however this soon limited adding extra metadata such as “preservation” type which I will implement later. I will now be using [meta] tags with variables inside them to allow for more advanced configuration!

0
0
3

Followers

Loading…