Classic confinment for the `palang` snap

store-requests classic-confinement
1

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.

2

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

3

The exception for classic confinement for compilers is that they usually require access to header or library files which are installed on the host system in locations like /usr/include etc - but it is not clear to me that this is the case for this snap - can you please clarify? Since if it only requires access to the project to be compiled etc then this can be achieved with the home and optionally removable-media interfaces.

4

Hi Alex, thank you for the feedback, I confirm that the home interface is sufficient for my needs here. The compiler does not need to access privileged directories like /usr. The standard library and profile configurations are stored in the local data directory (which is ~/.palang for the non-snap version) and project dependencies are stored in a gitignored subdirectory of the project.

I know the home interface only allows snaps to see non-hidden files and directories so I won’t see ~/.palang, but it makes sense to store local data under ~/snap/palang/... instead so that configurations and local data can be managed by the snap versioning system.

This request can be closed.

5

Thanks for confirming @Thinking-Dragon - I have removed this request from our internal queue.