freenode

← digests

Desktop and graphics: upgrades, AI policy, packages

Desktop & Graphics2026-08-24

GNU/Linux compatibility breakage and KDE AI governance led discussion, with Emacs packaging and KDE feature requests following. Several proposals sought clearer practices for long-lived software and desktop tools.

GNU/Linux upgrades breaking old programs

An RMS-initiated thread on emacs-devel examined how concrete GCC and Glibc changes break old Emacs builds after system upgrades. Participants explored distro and Emacs practice adjustments aimed at better long-term compatibility. Developers shipping or maintaining software across upgrades have a direct stake in the outcome.

KDE AI and LLM policy debate

A KDE Discourse thread debated project policy on AI and LLM usage. Clashes covered ethics, discrimination concerns, and AI-generated merge requests that overwhelm maintainers. The discussion may influence how KDE handles automated contributions and related governance rules.

project-store package for NonGNU ELPA

A submission proposed project-store, a project.el backend for Nix and Guix, for inclusion in NonGNU ELPA. Maintainers and RMS engaged in name bikeshedding during review. Emacs users who rely on Nix or Guix workflows may care about the packaging and naming resolution.

Dual places panels in Dolphin

Users requested dual places panels for Dolphin split view. The thread weighed usability tradeoffs against existing alternatives. People who work extensively in dual-pane file management have a reason to track whether the idea advances.

KRunner timer plugin idea

A user outlined a KRunner timer plugin using syntax such as remindme 5m and indicated a possible upstream PR. Participants discussed the approach and fit with existing tools. Plasma users who want quick timers from the runner interface may follow any resulting submission.

Magit-style Sapling interface for Emacs

A user sought NonGNU ELPA inclusion for a Magit-inspired VC package targeting Sapling (sl). Discussion covered packaging details, the VC backend, and naming. Emacs developers who use Sapling have an interest in whether the package lands and how it integrates.