Project Description
Before the openSUSE 2022, we built a prototype of a command line interface for D-Installer just for demonstration purposes. It implements a limited set of functions and, apart from packaging changes, it has not received any relevant update for months.
Recently, we have redefined how the CLI should look. We want to rebuild the CLI from scratch with the new design in mind. However, it sounds boring for a Hack Week project so, why not try something different?
The idea of this project is to rebuild the D-Installer's CLI using Rust. We want to explore how hard it could be compared to Ruby, the main language for D-Installer and YaST. So, if you are interested in learning Rust (and the internals of D-Installer), feel free to join the project.
Goal for this Hackweek
- Support for
config setandconfig show. - Start the installation and track the progress.
- (optional) Operate through an SSH connection
Resources
- Project's homepage
- Rust homepage
- zbus: library to interact with D-Bus.
- clap-rs: a full featured, fast Command Line Argument Parser for Rust.
- prodash: dashboard for displaying the progress of concurrent application.
Results from Hack Week 22
We have summarized our findings in a message to the yast-devel mailing list.
Looking for hackers with the skills:
This project is part of:
Hack Week 22
Activity
Comments
-
over 2 years ago by IGonzalezSosa | Reply
You can find the summary of the Hack Week 22 in this message to the yast-devel mailing list.
Similar Projects
Advent of Code: The Diaries by amanzini
Description
It was the Night Before Compile Time ...
Hackweek 25 (December 1-5) perfectly coincides with the first five days of Advent of Code 2025. This project will leverage this overlap to participate in the event in real-time.
To add a layer of challenge and exploration (in the true spirit of Hackweek), the puzzles will be solved using a non-mainstream, modern language like D, Crystal, Gleam or Zig.
The primary project intent is not just simply to solve the puzzles, but to exercise result sharing and documentation. I'd create a public-facing repository documenting the process. This involves treating each day's puzzle as a mini-project: solving it, then documenting the solution with detailed write-ups, analysis of the language's performance and ergonomics, and visualizations.
|
\ ' /
-- (*) --
>*<
>0<@<
>>>@<<*
>@>*<0<<<
>*>>@<<<@<<
>@>>0<<<*<<@<
>*>>0<<@<<<@<<<
>@>>*<<@<>*<<0<*<
\*/ >0>>*<<@<>0><<*<@<<
___\\U//___ >*>>@><0<<*>>@><*<0<<
|\\ | | \\| >@>>0<*<0>>@<<0<<<*<@<<
| \\| | _(UU)_ >((*))_>0><*<0><@<<<0<*<
|\ \| || / //||.*.*.*.|>>@<<*<<@>><0<<<
|\\_|_|&&_// ||*.*.*.*|_\\db//_
""""|'.'.'.|~~|.*.*.*| ____|_
|'.'.'.| ^^^^^^|____|>>>>>>|
~~~~~~~~ '""""`------'
------------------------------------------------
This ASCII pic can be found at
https://asciiart.website/art/1831
Goals
Code, Docs, and Memes: An AoC Story
Have fun!
Involve more people, play together
Solve Days 1-5: Successfully solve both parts of the Advent of Code 2025 puzzles for Days 1-5 using the chosen non-mainstream language.
Daily Documentation & Language Review: Publish a detailed write-up for each day. This documentation will include the solution analysis, the chosen algorithm, and specific commentary on the language's ergonomics, performance, and standard library for the given task.