For the next release of MiniZinc we were hoping to add the snap store as a new distribution medium for the MiniZinc bundle. We created a snap named
minizinc that contains both the MiniZinc compiler/driver and the MiniZinc IDE.
We would like to request classic confinement for this snap as were currently running into various limitations. One of MiniZinc’s main features is to interface with various optimisation solvers. Not all of these solvers are reachable in the strict confinement as they might be installed anywhere on the system. The IDE itself also doesn’t behave as expected within the strict confinement as it for instance cannot access the filesystem as the user knows it.
Let us know if there is any more information is required
Hi there, thanks for working on a snap of MiniZinc. Can you share a link to your snapcraft.yaml, please? It is possible that it can be strictly confined and we can take a quick look.
I’m happy to share our snapcraft configuration:
version-script: cat version.txt
summary: The MiniZinc bundle
MiniZinc is a free and open-source constraint modeling language. You can
use MiniZinc to model constraint satisfaction and optimization problems in
a high-level, solver-independent way, taking advantage of a large library
of pre-defined constraints. Your model is then compiled into FlatZinc, a
solver input language that is understood by a wide range of solvers.
command: bash $SNAP/MiniZincIDE.sh
As you can see we use binaries that are compiled in previous stages of our CI process. The main binaries are compiled from https://github.com/MiniZinc/libminizinc and https://github.com/MiniZinc/MiniZincIDE, but we also include some solvers from different sources.
We initially tried the strict confinement and used the interfaces plugs
home, network, opengl, x11 (also prepending
desktop-launch to the MiniZincIDE command). This gave us some basic functionality, but gave some strange errors. We also got feedback for some initial testers that IDE behaved strangely and that you can not connect to solvers that are not in your home directory.
I was just hoping to hear if there is any progress in the process. Is there any more information that we can provide?
Ping @moderators. Would anyone be able to give us an update on the process or at least provide us with a timeline for when we can expect some feedback on what to do with our snap?
Ping @Wimpress - the publisher responded to your question.
Ping @Wimpress - Just trying one last time. We’re planning the release for the beginning of next week so we’re really hoping to hear something back soon.
@MiniZinc Sorry for the delay in replying, it is holiday and conference season. I’ve downloaded the MiniZinc tarball bundle and had an experiment. I now better appreciate why classic confinement is desirable for you.
I’m happy to +1 the request for classic confinement but I would like to collaborate with you after the initial release to work towards strictly confining it as I think that will be possible in the near term.
@Wimpress - it isn’t clear from the response that the publisher has been vetted. Can you comment?
@Wimpress I’m glad to have the support. We’d be happy to look into the option of using a strict confinement if it won’t limit the functionality.
@jdstrand, I don’t know what kind of vetting is required, but we did have to acquire the “minizinc” name for the snap, so maybe some of this work has already been done.
@jdstrand I can verify that the minizinc publisher account is operated by Jip J. Dekker one of the core upstream contributors.
I’m +1 on this being classic too.
Given that MiniZinc depends on calling binaries that are not known at build time, I am +1 on the classic request.
@Wimpress - thanks!
Granting use of classic. This is now live.