The existing racket snap uses strict confinement, which is useful in some but not all cases. Racket contains an compiler, language-specific package manager (raco) and a full blown IDE (drracket). I would like to request that a specific track of racket to use classic confinement, while the default track stay on strict confinement.
In addition though, a snap must also have a requirement for classic confinement via the need to execute arbitrary binaries from the host, or access files outside the snap’s mount namespace from the host (eg. /usr/ etc) - however in the linked issue, the underlying problem seems to be that racket wants to access the emacs configuration for racket-mode - so I wonder if this could be solved by granting racketpersonal-files access to ~/.emacs.d/elpa which is the standard location where emacs packages are installed?
I think this makes sense for strict racket, but the nature of the problem is open-ended. I think having both confinement levels co-exist makes sense, as for some users the strictly confined version or the classically confined version will be simply more appropriate.
The requirements for classic for racket are understood are understood. As far as I know, the publisher has not been vetted previously so I will start that process now.
Thank you! I will discuss next steps upstream, as I suspect we want to help people migrate to the classic confined snap without having everyone stuck on the old version. I will look at publishing a classic snap to the beta channel tomorrow.
