Classic confinement request: gleam

[rroessler]

• Name: gleam
• Description: Gleam Programming Language
• Snapcraft: gleam-snap/snap/snapcraft.yaml at main · rroessler/gleam-snap · GitHub
• Upstream: GitHub - gleam-lang/gleam: ⭐️ A friendly language for building type-safe, scalable systems! · GitHub
• Upstream Relation: Contributor
• Supported Category: Programming Languages
• Reasoning: Gleam requires the use of either erlang or javascript and that is dependent on the users (eg: cannot determine this at build/install time as these could be external binaries). Additionally, the cache for global packages is hardcoded to ~/.cache/gleam in upstream code.

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.

[store-requests-bot]

This request has been added to the queue for review by the @reviewers team.

[shishirsub10]

Hi @rroessler

Requirements for classic are understood and +1 from me to grant classic to gleam. Publisher being Canonical employee is already vetted. Granting classic to gleam. New revision of the snap should automatically pass the review.

Also, if it is possible, it would be amazing to include the snap contents in the upstream repo.

[rroessler]

Hi @shishirsub10

Thanks for the quick response and review! Noted, so far in the process of chatting with upstream to see what they think.