Files
karim faaba27ed4 Display arrangement persistence + centering fix, packaging hardening
- core/display.py: write_positions() persists Arrangement's drag-and-drop
  layout into niri's config.kdl (one output { position x= y= } per output),
  validated via `niri validate` on a temp copy with a .kdl.bak backup before
  writing — same pattern as core/keybindings.py's rebind(). Previously the
  page only ever called `niri msg output … position set`, which niri treats
  as live-only and drops on the next login/reload.
- gui/pages/display.py: Arrangement's Apply now runs each output's `niri msg
  output … position set` synchronously instead of queuing them all on the
  single-shot ProcessRunner (which rejects a second run() while the first is
  still async) — a 2-monitor apply previously moved only the first output
  and silently dropped the rest. _dock_to_nearest keeps the free axis at the
  dragged position (so a shorter display can sit vertically centered next to
  a taller rotated one) rather than forcing corner alignment.
- core/panel.py, files/__init__.py: incidental fixes alongside the above.
- packaging/: signing-key generation script + build-user systemd setup for
  the [tanin] AUR auto-rebuild pipeline; PKGBUILD bumped to pkgrel=5.
- src/taninux/browser/: new module for browser theme sync (Fuji accent).
2026-07-13 14:19:50 +02:00

84 lines
2.6 KiB
Markdown

# TANINUX
Arch-based Linux distro (codename **camel**) built around the
[niri](https://github.com/YaLTeR/niri) scrollable-tiling Wayland compositor and
a GTK4 desktop with its own accent/theming system. Ships a central
maintenance TUI/GUI plus a small suite of first-party apps, distributed via a
custom `[tanin]` pacman repo and a Calamares-based installer ISO.
## The pillars
The central `taninux` app is organized around five pillars:
- **maintain** — scan and clean up (orphans, caches, leftover kernel modules)
- **update** — aggregate updates from pacman, AUR and flatpak
- **kernel** — install/remove kernel variants, boot-default management
- **suggest** — rule-based setup suggestions
- **health** — system health checks
## The apps
| Command | What it is |
|---|---|
| `taninux` | Maintenance TUI (Textual) |
| `taninux-gtk` | GTK4 shell |
| `tsettings` | Settings app (network, display, audio, users, …) |
| `thub` | Software Hub (repo/AUR/flatpak install) |
| `tfiles` | Native GTK4 file manager |
`tmusic` (TIDAL client) has moved to its own repo, `taninux-music`
(GPL-3.0, depends on `taninux[gui]`), and is no longer part of the base
ISO.
The GTK apps run on a custom libadwaita-free backend
(`src/taninux/gui/ui/native.py` + `style_apple.css`); `TANINUX_UI=adw`
selects the libadwaita backend.
## Installing
### On an existing Arch system
Add the `[tanin]` repo to `/etc/pacman.conf` (see
[docs/distribution.md](docs/distribution.md)), then:
```sh
pacman -S tanin-desktop # full desktop: niri + eww shell + apps
pacman -S taninux # just the maintenance tool
```
### Via the ISO
See [iso/BUILD.md](iso/BUILD.md) — archiso profile with a Calamares
installer (btrfs subvolume layout, snapper/snap-pac).
## Repo layout
```
src/taninux/ Python source: cli, gui, core, pillars, files, music
packaging/ PKGBUILDs + helper scripts for the [tanin] repo packages
iso/ archiso profile (build-profile/ + overrides/) and BUILD.md
distro/ distro-level manifest (camel.toml, MANIFEST.md)
docs/ distribution plan, eww integration contracts
scripts/demo/ visual QA scripts for the native UI backend
```
## Development
```sh
uv venv && uv pip install -e ".[gui]" # PyGObject/GTK4 come from pacman
taninux # TUI
TANINUX_UI=native tsettings # settings app, native backend
python scripts/demo/page_demo.py # render single pages for visual QA
```
## Building packages
```sh
cd packaging/<pkg> && makepkg -si # single package
./packaging/build-tanin-repo.sh # rebuild the whole [tanin] repo
```
## License
GPL-3.0-or-later — see [LICENSE](LICENSE).