Skip to content

chore(vcpkg-ports): Ecosystem port consistency audit fixes #558

Description

@kcenon

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

  • Every port dependency is actually used in the build
  • Every source core dependency has a corresponding port dependency
  • All feature dependency arrays are non-empty where a library is required
  • All portfiles use snake_case PACKAGE_NAME matching upstream CMake exports
  • vcpkg consumer integration test passes for all 8 packages

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions