Skip to main content

Crate corundum_framework_package

Crate corundum_framework_package 

Source
Expand description

A desktop app as a Velopack package.

start is the first thing an app’s main runs: Velopack’s own start, the Windows install and uninstall hooks, and which Start this is (the first, the first after an update, or neither), told from the version the app last ran with. Updater finds and downloads updates by itself and applies one only when asked, after the app’s before_apply.

Velopack packages the desktops only; on iOS and Android the crate is empty.

Re-exports§

pub use cli_path::CliSpec;

Modules§

cli_path
The app’s command line on PATH.
console
A console shim for a Windows GUI binary.

Structs§

PackageSpec
What a package needs from the app.
Updater
A package’s updates: one thread checks and downloads, the state is shared, and nothing is applied until Updater::apply. Clones share the thread and the state; the thread ends with the last clone.
Version
SemVer version as defined by https://semver.org.

Enums§

After
What happens once an update is applied, and who ends the process for it.
Error
What can go wrong with a package’s updates.
Source
Where a package’s updates are published.
Start
Which start this is, against the version the app last ran with.

Functions§

start
Velopack’s start, then what this start is. The first thing main runs but the app’s logging: started for a Windows hook, it runs the hook and exits, and what goes wrong in a hook (the command line not put on PATH) is only logged, so initialise logging before calling start.