MetaStripper — Licenses & Third-Party Notices

This folder contains third-party license materials shipped with MetaStripper.

What’s inside
- THIRD_PARTY_NOTICES.txt
  Human-readable summary of key third-party components and their licenses.
  This is the primary “what we use” notice for end users.

- THIRD_PARTY_PYTHON_MANIFEST.txt
  Technical dependency inventory (build/dev). Not a legal notice.
  Use it for troubleshooting and reproducible builds.

- qt/
  Qt / PySide6 licensing materials (LGPL/GPL texts and related notices).
  See LGPL_COMPLIANCE.md for practical compliance checklist.

- 7zip/
  7-Zip 26.02 license texts, source location, binary provenance, and hashes.
  MetaStripper bundles 7z.exe and 7z.dll for read-only RAR/RAR5 extraction.

- flag-icons/
  MIT license for the country and regional flag artwork used by locale menus.

- inno-setup/
  Inno Setup redistribution license covering the installer and translated
  message files. Commercial use also requires the appropriate Inno Setup
  commercial license from the vendor.

- openssl/
  OpenSSL 1.1 and 3.x license texts for the libssl/libcrypto DLLs required by
  the Python runtime in Windows builds.

- <package>/
  Full license texts bundled for specific components (LICENSE / NOTICE / COPYING, etc.)
  Example: pillow/, pyinstaller/, etc.

How to (re)generate / update (source/dev)
- Run:
    python tools/generate_licenses_bundle.py
  This updates the technical manifest and may copy license files from installed
  Python packages into licenses/<package>/ when available.

Packaged builds (Windows EXE)
- The build should bundle this entire “licenses” folder next to the executable.
- End users should be able to open this folder from the app (Help → Licenses / Open folder).

Important notes
- Some wheels do not include full license texts. If a required license text is missing,
  add it manually to this folder.
- The 7-Zip, flag-icons, Inno Setup, and OpenSSL sections in
  THIRD_PARTY_NOTICES.txt are generated separately from Python package metadata
  because they are native or artwork/build components rather than Python packages.
- Qt / PySide6 (LGPL) may require allowing users to replace/relocate Qt libraries.
  See LGPL_COMPLIANCE.md for the engineering checklist and practical steps.

Encoding
- Prefer UTF-8 (no BOM) for text files to avoid mojibake on Windows.
