LabVIEW Package Manager: Non‑Deterministic Dependency Resolution Causes Build Inconsistency

Symptom

LabVIEW Package Manager (LVM) 1.0 sometimes resolves conflicting or circular dependency constraints in a non‑deterministic manner, producing different dependency graphs on otherwise identical projects.

Goal

Determine how LVM’s resolver behaves when two packages declare incompatible version constraints for the same dependency, and whether the resolution order influences the final build.

Constraints & Uncertainty

• LVM uses semantic versioning but lacks a documented deterministic strategy for conflict resolution.
• Circular dependencies are unsupported, yet the resolver’s reaction to inadvertent cycles is not specified.
• Different team members may add packages in varying sequences, potentially altering the resolution outcome.

Questions

1. What deterministic resolution strategy could LVM adopt to guarantee identical dependency selections across all machines when conflicting constraints exist?
2. Can LVM be configured to enforce a fixed resolution order or lock file to preserve reproducibility?
3. How does the presence of a circular dependency affect the resolver’s ability to produce a repeatable build, and what safeguards can be introduced?