-
name: mise
- description: dev tools, env vars, task runner
- snapcraft: mise/snapcraft.yaml at main · jdx/mise · GitHub
- upstream: GitHub - jdx/mise: dev tools, env vars, task runner
- upstream-relation: self
- supported-category: tools for local, non-root user driven configuration of/switching to development workspaces/environments
- reasoning: mise is a development environment manager and task runner that operates on files throughout the user’s filesystem. It executes arbitrary user-defined tasks from configuration files (similar to make or npm run), installs and manages development tools by downloading binaries and running installation scripts from multiple backends (ASDF plugins, cargo, npm, GitHub releases), provides shell integration by installing shims and modifying shell configurations in arbitrary locations, and coordinates installed tools with version control systems, package managers, and container runtimes across the development environment. These operations require unrestricted filesystem access and command execution that strict confinement cannot provide.
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.