Hi, I’m requesting classic confinement for the ruff snap, but if possible I would like that to only be available to a latest-classic track.
- name: ruff
- description: The ruff linter for Python
- snapcraft: ruff/snap/snapcraft.yaml at candidate · snapcrafters/ruff · GitHub
- upstream: GitHub - astral-sh/ruff: An extremely fast Python linter and code formatter, written in Rust.
- upstream-relation: Unofficial snap published by snapcrafters, but with open communication with the developers
- supported-category: Debug tools(?)
- reasoning: This isn’t always necessary, but many CI tools (e.g. LPCI) place the source code in locations that are not accessible to strictly confined snaps under any known interfaces. Because most users would not need this, I would maintain two copies of the snap — the
latesttrack would exist as-is, but a secondarylatest-classictrack would be added to provide a classic snap for people who need this installed with classic confinement.
I understand that strict confinement is generally preferred over classic.
I’ve tried the existing interfaces to make the snap to work under strict confinement.