Module remove 

End-to-end package removal workflow for winbrew remove.

Removal is split into two phases so the CLI can reason about impact before it mutates anything:

• plan_removal loads the target package and collects dependent packages.
• execute_removal applies the plan and performs engine-specific cleanup.

The high-level remove helper simply composes those phases for callers that want a one-shot operation. The CLI typically uses the lower-level plan and execution functions separately so it can show a warning, ask for confirmation, and then decide whether to proceed.

Dependency checks are conservative by default. If a package is still required by another installed package, removal is blocked unless the caller explicitly opts into force. The plan itself is still built so the caller can see exactly which dependents were discovered.

Modules

execution 🔒

Engine-specific package removal and filesystem cleanup.

plan 🔒

Removal planning and dependency analysis.

Structs

RemovalPlan

The removal plan derived from installed-package state and dependents.

Enums

RemovalError

Errors produced by the removal workflow.

Functions

execute_removal

Execute package removal using a fresh database connection.

find_dependents

Find installed packages that depend on the named package.

plan_removal

Build a removal plan for the named package.

remove

Plan and execute package removal in one call.

Type Aliases

Result

Convenience result type for removal operations.