Skip to content

fix(packaging): ship upstream's THIRD-PARTY-NOTICES.txt instead of legal/ - #11

Closed
ryan-morris wants to merge 1 commit into
mainfrom
chore/third-party-notices
Closed

ryan-morris wants to merge 1 commit into
mainfrom
chore/third-party-notices

Conversation

@ryan-morris

Copy link
Copy Markdown
Member

devenvy/ffmpeg now builds with ffmpeg-build (devenvy/ffmpeg#60, merged). Its archives carry one THIRD-PARTY-NOTICES.txt at the root (the variant's license notice and every bundled library's license text) instead of the legal/ folder. This packs that file into the NuGet packages in place of legal/.

Merge before the next FFmpeg bump. The first ffmpeg-build releases (8.1.3.4, 9.0.2.4) are building now; once they're out, check-updates.yml will offer them, and packaging them needs this change.

🤖 Generated with Claude Code

…gal/

Upstream's archives moved to the ffmpeg-build engine, which drops the
legal/ directory and puts one THIRD-PARTY-NOTICES.txt at every archive's
root, the iOS xcframework bundle included. Packing still looked for
legal/, so every platform package would have shipped with no licence
text and failed verify-packages.py, and the Apple packages had no
notices to copy at all.

- pack.sh moves the archive's notices file to the package root (never
  under runtimes/{rid}/native/, where NuGet would copy it into every
  consumer's output) and copies the iOS bundle's into each Apple
  package; an archive without one fails the pack
- Runtime.csproj and Apple.csproj pack THIRD-PARTY-NOTICES.txt at the
  package root
- verify-packages.py requires it at the root of every platform package
  and rejects a copy anywhere else
- audit-upstream.py reports has_notices instead of has_legal
- README and the design spec describe the new file

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ryan-morris

Copy link
Copy Markdown
Member Author

Folded into #12, so there's one PR to merge.

@ryan-morris
ryan-morris deleted the chore/third-party-notices branch October 15, 2026 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant