Updates

The crate works on both Flatpak installations at once: every system installation and the user installation. All functions block, so call them from a worker thread. The progress callback runs on the calling thread, from inside the call.

Example

use atlas_framework_flatpak as flatpak;

// What is available (refresh = true updates remote summaries and appstream data first, over the network).
for u in flatpak::list_updates(true)? {
    println!("{} {} ({} bytes)", u.name, u.branch, u.download_size);
}

// Run the updates, holding back apps that ask for new permissions.
let opts = flatpak::UpdateOptions { hold_new_permissions: true, ..Default::default() };
let outcome = flatpak::update(&opts, |p| eprintln!("{}: {}%", p.reference, p.percent));
for h in &outcome.held_back {
    println!("{} wants: {:?}", h.app.name, h.permissions);
}
if let Some(e) = outcome.error {
    eprintln!("an update failed: {e}");
}

Functions

UpdateOptions

#[derive(Debug, Clone, Copy, Default, PartialEq, Eq)]. All fields default to false.

Types

All derive Debug, Clone, PartialEq, Eq unless noted.

Errors and text from remotes

pub struct Error(pub String) implements Debug, Display and std::error::Error, and converts from a glib error. The message is cleaned and cut to 300 characters, because flatpak's messages can carry text from a remote. pub type Result<T> = std::result::Result<T, Error>.

Text from a remote (app names, versions, permission items) should be made safe before it is shown or logged: