Expand description
Spawn commands outside the sandbox or monitor if the running application has received an update & install it.
§Examples
Spawn a process inside of the sandbox, only works in a Flatpak.
use std::collections::HashMap;
use ashpd::flatpak::{Flatpak, SpawnFlags, SpawnOptions};
async fn run() -> ashpd::Result<()> {
let proxy = Flatpak::new().await?;
proxy
.spawn(
"/",
&["contrast"],
HashMap::new(),
HashMap::new(),
SpawnFlags::ClearEnv | SpawnFlags::NoNetwork,
SpawnOptions::default(),
)
.await?;
Ok(())
}
Structs§
- The Development interface lets any client, possibly in a sandbox if it has access to the session helper, spawn a process on the host, outside any sandbox.
- The interface exposes some interactions with Flatpak on the host to the sandbox. For example, it allows you to restart the applications or start a more sandboxed instance.
- Specified options for a
Flatpak::spawn
request. - A response containing the update information when an update is available.
- The interface exposes some interactions with Flatpak on the host to the sandbox. For example, it allows you to restart the applications or start a more sandboxed instance.
- A response of the update progress signal.
Enums§
- Flags affecting the running of commands on the host
- A bitmask representing the “permissions” of a newly created sandbox.
- Flags affecting the created sandbox.
- Flags marking what optional features are available.
- The update status.