Devpack-for-rust: classic confinement request

[petrakat]

Hello,

• name: devpack-for-rust
• description: Zero to Rust in seconds. An install wizard for Rustup, IDE, and Rusty tools
• snapcraft: https://github.com/canonical/devpack-for-rust/blob/main/snapcraft.yaml
• upstream: https://github.com/canonical/devpack-for-rust
• upstream-relation: Unaffiliated
• supported-category: “tools for local, non-root user driven configuration of/switching to development workspaces/environments”
• reasoning: The tool requires running apt and snap to install software. devpack-for-rust is run as sudo, and drops permissions as needed to invoke tools that must be run as the user (like rustup)

It is a Canonical roadmap item and I am requesting this in my capacity as a Canonical developer.

Please let me know if you need any more information – thanks!

[ogra]

You might want to use the template:

About the classic-confinement category

This category is for handling requests for classic confinement. The process is documented in Classic confinement review process. To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant. name: name of the snap description: description of the snap snapcraft: URL pointing to the snapcraft.yaml if publicly available upstream: URL pointing to the upstream repository, if open-source…

You will also need to specify a supported category, the list can be found in the document below:

Reviewing classic confinement snaps

[store-requests-bot]

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.

[petrakat]

Hello, I have updated the snap. (I had to rewrite it quite a bit to adhere to the Snap guidelines; my apologies for the delay.)