The SystemVerilog constraint behind the registry, resolver, lockfile, and filelist.
How DVLib thinks about packages
Why exactly one version wins
DVLib uses familiar package-manager ideas, but SystemVerilog package names live in one global namespace. A simulation cannot safely elaborate two unrelated copies of the same package the way a JavaScript project can nest dependency versions. The resolver therefore selects one version of every package name that satisfies every direct and transitive constraint.
The five artifacts in the workflow
| Artifact | Role |
|---|---|
| dvlib.toml | Declares package identity, compile inputs, and version ranges. |
| Registry | Stores immutable package archives and exposes package metadata. |
| dvlib.lock | Pins the resolved graph, checksums, dependency edges, and dev flags. |
| dvlib_packages/ | Project-local installation directory, one directory per package name. |
| dvlib.f | Simulator-neutral filelist in dependency and manifest compile order. |
Publish once, reproduce many times
A producer publishes a named semantic version. A consumer declares ranges and runs install. DVLib resolves the graph, downloads or reuses cached archives, verifies SHA-256 checksums, installs the selected versions, writes the lockfile, and emits the filelist. Later installs reuse the lock pins unless update explicitly asks for a new resolution.