To make the review of your request easier, please place it in the appropriate subcategory (classic-confinement, privileged-interfaces, aliases, tracks, transfer-ownership or guardrail). You can use the dropdown menu to choose the subcategory as shown in the following image:
Hello,
I would like to request classic confinement for my snap aed-dsa.
AED (Disk Space Analyzer) is a terminal-based interactive disk usage explorer, written in Go. It functions similarly to ncdu.
To be useful, the application needs to scan the entire filesystem (including /var, /usr, and mounted external drives) to report space usage to the user. Strict confinement limits the scan to the snap’s own sandbox or home directory, which defeats the purpose of a full system disk analyzer.
The source code is available here: GitHub - Quirky1869/AED: Analyseur d'espace disque en Go - Disk space analyzer in Golang
Thank you!
This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.
Hey @quirky1869
It is plausible that there are technical reasons why aed-dsa needs classic to work properly in all scenarios, but please note that classic confinement is a sensitive matter and it is reserved for mature, well-known applications published by mature, well-known entities. As of today, I believe that aed-dsa doesn’t meet this criteria because of the following reasons:
-
The project seems to be very fresh, according to the upstream repository
-
The projects seems to have little/none community around according to upstream repository (contributors, issues, PRs, etc.)
-
I could not find evidences that the project has a strong enough user base currently
Thus, considering these factors, I think aed-dsa should not get classic confinement as of now.
