Hello,
I recently published “atualiza-go” and requested classic confinement, which is currently held for manual review. I’d like to provide more context on why this is necessary for the application’s core functionality.
I’m a Software Engineer and Electronics Specialist, and I’ve recently started contributing to the open-source ecosystem by publishing apps.
Technical Challenge: “atualiza-go” is a unified graphical frontend designed to simplify system maintenance across different Linux families (Debian, Arch, Fedora, openSUSE, etc.).
To achieve this, the application needs:
Multi-distro binary access: It executes native package managers (apt, dnf, pacman, zypper, apk, xbps, eopkg). There is currently no set of strict interfaces that provides access to all these different package managers across varying host distributions. Host environment detection: It must identify the host distribution via /etc/os-release and verify the presence of specific binaries to apply the correct update logic. Under strict confinement, the app only sees the core22 base environment. Privileged execution: It uses pkexec to run these maintenance tasks with user authorization. Current State: In strict confinement, the app functions only as a read-only telemetry dashboard, which defeats its purpose as an active system updater.
I am not trying to replace system package managers, but rather provide a consistent, user-friendly interface for them. I would appreciate it if you could clarify if classic is the right path for this multi-distro utility or if there is a recommended set of interfaces that could support such a broad range of native tools.
Thanks in advance for your time and guidance.
Erasmo Cardoso Software Engineer | Electronics Specialist