-
Simon McVittie authored
In the case where we use Flatpak sub-sandboxing, we're not going to be building a bubblewrap command-line at all. Luckily, when we make use of a mutable sysroot, we don't need it. This requires splitting bind_runtime(), which consists of * a part that builds up the basic bwrap command-line and environment variables before setting up the graphics stack (now bind_runtime_base()) * setting up the graphics stack by either building a bwrap command-line or editing the mutable sysroot, and in either case setting environment variables (pv_runtime_use_provider_graphics_stack()) * a final part that sets the last few bwrap arguments and exports (bind_runtime_finish(), which can't currently fail) Signed-off-by:
Simon McVittie <smcv@collabora.com>
Simon McVittie authoredIn the case where we use Flatpak sub-sandboxing, we're not going to be building a bubblewrap command-line at all. Luckily, when we make use of a mutable sysroot, we don't need it. This requires splitting bind_runtime(), which consists of * a part that builds up the basic bwrap command-line and environment variables before setting up the graphics stack (now bind_runtime_base()) * setting up the graphics stack by either building a bwrap command-line or editing the mutable sysroot, and in either case setting environment variables (pv_runtime_use_provider_graphics_stack()) * a final part that sets the last few bwrap arguments and exports (bind_runtime_finish(), which can't currently fail) Signed-off-by:
Simon McVittie <smcv@collabora.com>