Struct aur_depends::Actions

pub struct Actions<'a> {
    pub missing: Vec<Missing>,
    pub unneeded: Vec<Unneeded>,
    pub build: Vec<Base>,
    pub install: Vec<RepoPackage<'a>>,
    /* private fields */
}

The response from resolving dependencies.

Note that just because resolving returned Ok() does not mean it is safe to bindly start installing these packages.

Fields

missing: Vec<Missing>

Some of the targets or dependencies could not be satisfied. This should be treated as a hard error.

unneeded: Vec<Unneeded>

Targets that are up to date.

build: Vec<Base>

Aur packages to build.

install: Vec<RepoPackage<'a>>

Repo packages to install.

Implementations

impl<'a> Actions<'a>

pub fn iter_aur_pkgs(&self) -> impl Iterator<Item = &AurPackage>

An iterator over each AUR package in self.build.

pub fn iter_custom_pkgs(
    &self
) -> impl Iterator<Item = (&Srcinfo, &CustomPackage)>

An iterator over each custom package in self.build.

impl<'a> Actions<'a>

pub fn calculate_conflicts(&self, makedeps: bool) -> Vec<Conflict>

Calculate conflicts. Do note that even with conflicts it can still be possible to continue and install the packages. Although that is not checked here.

For example installing pacman-git will conflict with pacman. But the install will still succeed as long as the user hits yes to pacman’s prompt to remove pacman.

However other cases are more complex and can not be automatically resolved. So it is up to the user to decide how to handle these.

makedeps: if true, include make dependencies in the conflict calculation.

pub fn calculate_inner_conflicts(&self, makedeps: bool) -> Vec<Conflict>

Calculate inner conflicts. Do note that even with conflicts it can still be possible to continue and install the packages. Although that is not checked here.

For example installing pacman-git will conflict with pacman. But the install will still succeed as long as the user hits yes to pacman’s prompt to remove pacman.

However other cases are more complex and can not be automatically resolved. So it is up to the user to decide how to handle these.

makedeps: if true, include make dependencies in the conflict calculation.

pub fn duplicate_targets(&self) -> Vec<String>

Find duplicate targets. It is possible to have duplicate targets if packages with the same name exist across repos.

Trait Implementations

impl<'a> Debug for Actions<'a>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.