What
Synchronize all 8 overlay port definitions in vcpkg-ports/ with the canonical vcpkg-registry (kcenon/vcpkg-registry). The overlay ports have diverged from the registry across versions, port-versions, dependencies, portfile structure, and patching approach.
- Current: Overlay ports use hardcoded git SHA/tag REFs, manual patches, and legacy snake_case wrappers. Three systems have stale versions (thread 0.3.0, logger 0.1.2, network 0.1.0).
- Expected: Overlay ports mirror the registry's
v${VERSION} template approach, current versions, and feature-based options.
- Scope:
monitoring_system/vcpkg-ports/ directory only.
Divergence Summary
| System |
Overlay Version |
Registry Version |
Overlay pv |
Registry pv |
Status |
| common_system |
0.2.0 |
0.2.0 |
0 |
0 |
Match |
| thread_system |
0.3.0 |
0.3.1 |
- |
- |
Version mismatch |
| logger_system |
0.1.2 |
0.1.3 |
2 |
- |
Version mismatch |
| container_system |
0.1.0 |
0.1.0 |
1 |
2 |
Port-version mismatch |
| monitoring_system |
0.1.0 |
0.1.0 |
0 |
1 |
Port-version mismatch |
| database_system |
0.1.0 |
0.1.0 |
3 |
3 |
Deps/features diverged |
| network_system |
0.1.0 |
0.1.1 |
5 |
1 |
Full divergence |
| pacs_system |
0.1.0 |
0.1.0 |
5 |
4 |
Port-version + features |
Why
- Overlay ports serve as local CI validation staging area. When they diverge from the registry, local validation tests different code than what consumers install.
- Three version mismatches mean the overlay validates outdated source code.
- Missing features in overlay (database backends, pacs codecs/storage) means local CI cannot test feature-based builds.
Where
vcpkg-ports/kcenon-thread-system/ — version + portfilevcpkg-ports/kcenon-logger-system/ — version + portfilevcpkg-ports/kcenon-network-system/ — version + portfile + dependencies + featuresvcpkg-ports/kcenon-container-system/ — port-version + portfilevcpkg-ports/kcenon-monitoring-system/ — port-version + portfilevcpkg-ports/kcenon-database-system/ — dependencies + features + portfilevcpkg-ports/kcenon-pacs-system/ — port-version + features + portfile- Related:
kcenon/vcpkg-registry (source of truth)
How
Technical Approach
- Phase 1 — Version fixes (thread, logger, network): Copy registry vcpkg.json + portfile.cmake, remove obsolete patches
- Phase 2 — Port-version alignment (container, monitoring, pacs): Update vcpkg.json port-version, sync portfile changes
- Phase 3 — Dependency/feature alignment (database, network, pacs): Add missing features and dependencies from registry
- Phase 4 — Structural modernization: Migrate hardcoded REF →
v${VERSION}, remove patches incorporated upstream
Acceptance Criteria
What
Synchronize all 8 overlay port definitions in
vcpkg-ports/with the canonical vcpkg-registry (kcenon/vcpkg-registry). The overlay ports have diverged from the registry across versions, port-versions, dependencies, portfile structure, and patching approach.v${VERSION}template approach, current versions, and feature-based options.monitoring_system/vcpkg-ports/directory only.Divergence Summary
Why
Where
vcpkg-ports/kcenon-thread-system/— version + portfilevcpkg-ports/kcenon-logger-system/— version + portfilevcpkg-ports/kcenon-network-system/— version + portfile + dependencies + featuresvcpkg-ports/kcenon-container-system/— port-version + portfilevcpkg-ports/kcenon-monitoring-system/— port-version + portfilevcpkg-ports/kcenon-database-system/— dependencies + features + portfilevcpkg-ports/kcenon-pacs-system/— port-version + features + portfilekcenon/vcpkg-registry(source of truth)How
Technical Approach
v${VERSION}, remove patches incorporated upstreamAcceptance Criteria
v${VERSION}template.patchfiles removed (upstream fixes incorporated)validate-vcpkg-chainCI passes on all 3 platforms