Skip to content

📋 Vendored Dependencies Metadata

This directory contains metadata and tracking files for all vendored dependencies.

Files

vendored_versions.lock

Master lock file tracking all vendored dependencies.

Contains: - Exact versions and commits - Repository URLs - Installation dates and sizes - License information - Update policies - Dependency count and total size

Purpose: Reproducible builds, audit trail, dependency tracking

Format: YAML

Do not edit manually - use ../scripts/update_vendored.ps1 to modify.

juce_config.yaml

JUCE-specific configuration file.

Contains: - JUCE version and commit - Enabled/disabled modules - License type (Commercial/GPL) - Update policy - Installation metadata

Purpose: Track JUCE configuration and module selection

Format: YAML

juce_installed_version.txt

Quick version reference for JUCE.

Contains: Single line with version number (e.g., "7.0.9")

Purpose: Fast version checks in scripts and tools

Format: Plain text

Adding Metadata for New Dependencies

When vendoring a new dependency:

  1. Create [name]_config.yaml: 

    name: DependencyName
version: X.Y.Z
commit: abc123...
license: MIT
# ... other config

  2. Update vendored_versions.lock: Add entry to vendored_dependencies section

  3. Optional: Create [name]_installed_version.txt: For quick version checks

Maintenance

  • Review vendored_versions.lock regularly
  • Update lock file when dependencies change
  • Keep config files in sync with actual installations
  • Document all changes in lock file's update_history

See Also