ogra:
regarding the latter, yes, they should be classic. being tools that compile random bits in random places on the filesystem, need to check for availability of dependencies etc etc …
i would also snap them separately and not maintain the snap myself but instead try to convince the respective upstreams to adopt the snapcraft.yaml into their tree and maintain them collaboratively under an upstream name/account so it can be properly vetted.
Yes that’s what my plan is to. Also, I know that’s not fair but the blueprint-compiler thread needs some attention, cause it needs classic and it’s stuck almost a month now.
Blueprint Compiler is a compiler for the blueprint files. Blueprint is a markup language for GTK user interface files. This is the website for blueprint-compiler
https://gitlab.gnome.org/jwestman/blueprint-compiler
As this snap will be mostly used during snap compilations as a build snap, it needs to access all the files of the OS, which is not possible with confinement. Though, I never tried with a snap compilation to compile with blueprint-compiler and home plug, but I don’t think it’d work …
Kindly help on this also.
