What
Tracking epic for vcpkg port consistency issues identified during a comprehensive audit of all 8 ecosystem packages. The audit compared source vcpkg.json manifests against port vcpkg.json manifests and portfiles, checking dependency accuracy, feature parity, and naming conventions.
- Current: Several discrepancies between source manifests and port definitions
- Expected: Ports accurately reflect source dependencies, features are correctly wired, and naming conventions are uniform
- Scope:
vcpkg-ports/ overlay ports in this repository + kcenon/vcpkg-registry
Why
- Contradictory dependencies waste build time (e.g., logger_system port declares thread_system but disables it)
- Missing dependencies cause consumer build failures (e.g., network_system port missing zlib)
- Empty feature dependency arrays silently omit required libraries
- PascalCase→snake_case wrapper files add maintenance burden now that upstream has migrated
Where
| System |
Issue |
Severity |
| logger_system port |
Declares kcenon-thread-system dep but portfile sets -DLOGGER_USE_THREAD_SYSTEM=OFF |
High |
| network_system port |
Missing zlib core dependency (source declares it) |
High |
| monitoring_system port |
network feature has empty dependencies array |
Medium |
| logger/container/database/network ports |
PascalCase PACKAGE_NAME with wrappers despite upstream snake_case migration |
Medium |
| pacs_system source |
sqlite3 override version mismatch with database_system |
Low |
How
Sub-Issues
Acceptance Criteria
What
Tracking epic for vcpkg port consistency issues identified during a comprehensive audit of all 8 ecosystem packages. The audit compared source
vcpkg.jsonmanifests against portvcpkg.jsonmanifests and portfiles, checking dependency accuracy, feature parity, and naming conventions.vcpkg-ports/overlay ports in this repository +kcenon/vcpkg-registryWhy
Where
kcenon-thread-systemdep but portfile sets-DLOGGER_USE_THREAD_SYSTEM=OFFzlibcore dependency (source declares it)networkfeature has empty dependencies arrayPACKAGE_NAMEwith wrappers despite upstream snake_case migrationHow
Sub-Issues
Acceptance Criteria