Hello,
I need classic confinement for the snap stirmake. It’s a new build tool, needing access to shell commands and the current directory. Similar to cmake that uses classic confinement too, I think I have even more reasons for classic confinement than cmake has, since cmake just creates Makefiles, my build system executes the shell commands too that would be executed by GNU make in case of cmake.
Also stirmake would benefit from aliases smka, smkt and smkp. They are the standard documented way to execute stirmake, and all have the “smk” prefix referring to stirmake. Having to type “stirmake.smka” is contrary to the performance of the build system: I intend it to be very fast, in which case typing the command manually is the largest overhead, as the execution happens in an insignificant fraction of a second.
The user’s guide is here: Scalable true implementation of recursive make (stirmake), user's guide
- name: stirmake
- description: a new build tool that handles recursion better than GNU make
- snapcraft: not publicly available right now but I can make it available if needed
- upstream: URL pointing to the upstream repository, if open-source. Otherwise, ‘PRIVATE’
- upstream-relation: I’m the sole author of stirmake
- supported-category: compilers, more specifically build tools
- reasoning: the build tool needs to be able to execute arbitrary commands to build targets, and needs to be able to access the current directory to search for Stirfiles and check modification times of targets and sources
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.