Skip to content

Standardize vcpkg.json following ecosystem conventions #297

Description

@kcenon

Summary

Standardize vcpkg.json to follow the unified_system ecosystem conventions established in common_system.

Parent Epic

Part of kcenon/common_system#251 (Epic: vcpkg.json Standardization Across Unified System Ecosystem)

Current Status

database_system vcpkg.json is partially standardized (has $schema, version, description, homepage, license, testing feature).

Current Issues

Field Current Expected
name database-system kcenon-database-system
port-version missing add (0)
supports missing add "!(uwp | xbox)"
kcenon-common-system dependency missing add

Required Changes

  1. Package name: database-systemkcenon-database-system
  2. Add: port-version, supports
  3. Add: Ecosystem dependencies (kcenon-common-system, kcenon-thread-system, etc.)

vcpkg.json Template (partial update)

{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "name": "kcenon-database-system",
  "version": "1.0.0",
  "port-version": 0,
  "description": "Advanced C++20 Database System with Multi-Backend Support",
  "homepage": "https://github.com/kcenon/database_system",
  "license": "BSD-3-Clause",
  "supports": "!(uwp | xbox)",
  "dependencies": [
    "kcenon-common-system",
    "kcenon-thread-system",
    "kcenon-container-system",
    { "name": "fmt", "version>=": "10.2.1" },
    "asio"
  ],
  "features": {
    // ... existing features preserved
  }
}

Acceptance Criteria

  • vcpkg.json follows ecosystem standard template
  • All ecosystem dependencies declared
  • vcpkg manifest mode build succeeds

Metadata

Metadata

Assignees

Labels

architectureArchitectural changes and design

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions