pub enum Command {
Build {
all: bool,
project: Option<String>,
package: PackageType,
rpm_opts: RpmOpts,
flatpak_opts: FlatpakOpts,
oci_opts: OciOpts,
},
Clean,
List,
Init {
path: PathBuf,
yes: bool,
},
Completion {
shell: Shell,
},
CI,
Update {
labels: Vec<String>,
filters: Vec<String>,
excludes: Vec<String>,
},
Run {
scripts: Vec<String>,
labels: Option<String>,
},
}Variants§
Build
Build a project
This is the main entrypoint of Andaman.
This command optionally accepts a project name to build, or an --all flag to build all projects in the manifest.
If no project name is specified, and the --all flag is not specified, the program will exit with an error.
Fields
package: PackageTypeBuilds a specific artifact format
flatpak_opts: FlatpakOptsOptions for Flatpak builds
Clean
Cleans up the build directory
List
Lists all projects in the manifest
Init
Initializes a new project manifest
Completion
Generate shell completions
CI
Get CI output for Github Actions
Update
Update all projects
Fields
filters: Vec<String>Only run update scripts in project with the specified labels
This should be a comma-separated list of filters.
Each time --filters=... is specified, the comma-separated list of key-values will be
checked against a project. If missing or different, the project will be ignored.
However, specifying --filters multiple times will create an “or” effect — the
project will not be ignored if it satisfies one of the list of --filters. For
example, -f a=1,b=2 -f c=3 means the project needs to satisfy either “a=1” and “b=2”,
or only “c=3”.
excludes: Vec<String>Exclude update scripts in project with the specified labels
This should be a comma-separated list of excludes.
Each time --exclude=... is specified, the comma-separated list of key-values will be
checked against the labels of a project, and it will be ignored if all the key-values
are present. In addition, specifying --exclude multiple times will create an “or”
effect — a project will be excluded if it satisfies one of the list of --filters.
For example, -e a=1,b=2 -e c=3 means projects with “a=1” and “b=2” at the same time,
or “c=3”, are excluded. Projects with only “a=1” or “b=2” are not excluded.
This will always override --filters.
Run
Run .rhai scripts
Trait Implementations§
Source§impl FromArgMatches for Command
impl FromArgMatches for Command
Source§fn from_arg_matches(__clap_arg_matches: &ArgMatches) -> Result<Self, Error>
fn from_arg_matches(__clap_arg_matches: &ArgMatches) -> Result<Self, Error>
Source§fn from_arg_matches_mut(
__clap_arg_matches: &mut ArgMatches,
) -> Result<Self, Error>
fn from_arg_matches_mut( __clap_arg_matches: &mut ArgMatches, ) -> Result<Self, Error>
Source§fn update_from_arg_matches(
&mut self,
__clap_arg_matches: &ArgMatches,
) -> Result<(), Error>
fn update_from_arg_matches( &mut self, __clap_arg_matches: &ArgMatches, ) -> Result<(), Error>
ArgMatches to self.Source§fn update_from_arg_matches_mut<'b>(
&mut self,
__clap_arg_matches: &mut ArgMatches,
) -> Result<(), Error>
fn update_from_arg_matches_mut<'b>( &mut self, __clap_arg_matches: &mut ArgMatches, ) -> Result<(), Error>
ArgMatches to self.Source§impl Subcommand for Command
impl Subcommand for Command
Source§fn augment_subcommands<'b>(__clap_app: Command) -> Command
fn augment_subcommands<'b>(__clap_app: Command) -> Command
Source§fn augment_subcommands_for_update<'b>(__clap_app: Command) -> Command
fn augment_subcommands_for_update<'b>(__clap_app: Command) -> Command
Command so it can instantiate self via
FromArgMatches::update_from_arg_matches_mut Read moreSource§fn has_subcommand(__clap_name: &str) -> bool
fn has_subcommand(__clap_name: &str) -> bool
Self can parse a specific subcommand