vapoursynth-vszip 22.1.0 (new formula)

[cho-m]

This doesn't meet notability but considering an exception to simplify

• vsview 0.10.0 #298713

Zig makes it harder to pass our -headerpad_max_install_names (usually don't see an issue as most Zig dependents are executables rather than libraries).

Here the default @rpath/... is actually okay to use since the library is a plugin loaded by VapourSynth so can use preserve_rpath. Seemed safer to isolate this DSL usage to a separate formula and also allows scoping the Zig dependency, which is fragile and will keep breaking across releases until zig 1.0.

The parent package that introduces dependency does meet our notability requirement: https://github.com/Jaded-Encoding-Thaumaturgy/vs-jetpack (just barely at 77 stars)

---

Also, loading VapourSynth plugins is a bit complicated and won't work correctly in virtualenv. We will likely need to add VAPOURSYNTH_EXTRA_PLUGIN_PATH but this only accepts a single path and a user may want to override this at runtime.

---

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?
• Is your test running fine brew test <formula>?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

• I did not use AI/LLM to create this PR, or I disclosed the tool/model below and reviewed its output; I did not attribute commits to AI and will answer maintainer questions and review comments myself without AI/LLM.

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.