Skip to content

Discuss: Git LFS strategy for large binary files #48

@tobias-weiss-ai-xr

Description

@tobias-weiss-ai-xr

Context

The .gitattributes cleanup (PR #41) revealed several large binary files in the repo that could benefit from Git LFS:

Path Description
Common/3dParty/libvlc/build/** VLC precompiled binaries (~302 MB, 5 platforms)
Common/DesktopEditor/xmlsec/src/wasm/** Emscripten WASM binaries
Test/Applications/**/bin/** Compiled test binaries
Test/Applications/**/obj/** Compiled test objects

Open questions

  • Can libvlc binaries be removed entirely once vgpkg is in place? (@juliusknorr)
  • Are the WASM binaries still needed? (@rikled)
  • Can compiled test artifacts be dropped or generated via CI? (@DmySyz)
  • If any remain, should we use Git LFS, build from source, or package separately?

Proposal

Decide which binaries to remove vs. keep, then implement the chosen strategy in a follow-up PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions