Philip Peterson
cc654f6092
LadybirdBrowser/ladybird already maintains a complete, actively CI-tested flatpak manifest at Meta/CMake/flatpak/org.ladybird.Ladybird.json, built and tested on every commit/PR via their own .github/workflows/flatpak.yml (x86_64 + aarch64, currently green across the 10 most recent runs). It takes a fundamentally different approach than the manifest this repo had been building independently: every dependency is its own plain Flatpak module with a git-tag source, entirely bypassing vcpkg -- sidestepping essentially every problem the independent attempt spent this session working through (vcpkg bootstrap, googlesource archive non-reproducibility, build-time network deps, etc). Discovered while fixing the very last vendoring gap in the independent manifest (a real CI run had just compiled 68 of 69 vcpkg ports successfully). Maintaining a second, independent manifest against a fast-moving browser codebase when a first-party one already exists and stays in lockstep with the code by construction isn't a good use of ongoing effort. The independent vcpkg-based manifest and everything learned building it is preserved on the `vcpkg-approach` branch, not deleted. This repo now just clones LadybirdBrowser/ladybird and builds their manifest locally (Taskfile.yml: clone, build, run), rather than maintaining any manifest of its own. No Flathub submission for org.ladybird.Ladybird was found anywhere (flathub/flathub, the flathub org) as of this commit -- since upstream owns the manifest, they're the natural ones to submit it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
3 lines
29 B
Text
3 lines
29 B
Text
ladybird/
|
|
*.flatpak
|
|
.vscode/
|