Red Bear OS e45ce4d57a installer: add config-level package groups (Phase 3)
PackageGroup struct with description + package list. Groups are defined
in [[package_groups.NAME]] TOML sections and resolved by
resolve_package_groups() during Config::from_file(). Supports nested
groups (groups referencing other groups) with cycle detection.
Explicit [packages] entries override group membership.

Adds PartialEq derive to PackageConfig for dedup during merge.
3 unit tests: nested groups, explicit override, no-groups compat.
2026-06-30 15:59:02 +03:00

Redox OS installer

The Redox installer will allow you to produce a Redox OS image. You will be able to specify:

  • Output device (raw image, ISO, QEMU, VirtualBox, drive)
  • Filesystem
  • Included packages
  • Method of installation (from source, from binary)
  • User accounts

You will be prompted to install dependencies, based on your OS and method of installation. The easiest method is to install from binaries.

Usage

It is recommended to compile with cargo, in release mode:

cargo build --release

By default, you will be prompted to supply configuration options. You can use the scripted mode by supplying a configuration file:

cargo run --release -- config/example.toml

An example configuration can be found in config/example.toml. Unsuplied configuration will use the default. You can use the general.prompt setting to prompt when configuration is not set. Multiple configurations can be specified, they will be built in order.

Embedding

The installer can also be used inside of other crates, as a library:

# Cargo.toml
[dependencies]
redox_installer = "0.1"
// src/main.rs
extern crate redox_installer;

fn main() {    
    let mut config = redox_installer::Config::default();
    ...
    redox_installer::install(config);
}
S
Description
RedBear Operating System, based on RedoxOS. Licenced under MIT license.
https://redbearos.org
Readme MIT 20 GiB
Languages
C 43.9%
C++ 23.5%
Makefile 7.3%
Python 3.7%
JavaScript 3.4%
Other 17.1%