common: Split up socket setup from flatpak-run into multiple files #5411
Conversation
flatpak-run is large enough to be getting unwieldy, so separate it out into various smaller modules. A side benefit of these is that they'll be easier to reuse in other projects, like Steam's pressure-vessel tool. Signed-off-by: Simon McVittie <smcv@collabora.com>
|
The downside is if you want to understand what flatpak-run does then you need to inspect several files instead of one. |
That's already the case: flatpak-run is high-level functionality that has tentacles in most of Flatpak, including bwrap, context, exports, and even dir (because it needs to be able to find deployments and extensions). |
|
Yeah although I specifically meant how sandbox is created (which system sockets, paths, etc. are mounted). Previously all of those were in |
|
Everybody will have a different taste. I like not having |
flatpak-run is large enough to be getting unwieldy, so separate it out into various smaller modules.
A side benefit of these is that they'll be easier to reuse in other projects, like Steam's pressure-vessel tool.