Skip to content

Conversation

@bgilbert
Copy link
Collaborator

patch_url points to a redirect on wrapdb.mesonbuild.com, which is convenient if we ever want to add additional mirrors or if we have to move off of GitHub. However, it also means wraps will fail to build if wrapdb.mesonbuild.com goes down, unless the patch is already cached locally. Avoid this by adding a patch_fallback_url pointing directly to the GitHub download.

Conversely, source_fallback_url points directly at the source mirror in the GitHub release, which means we can't retroactively add additional mirrors or move existing releases off of GitHub. Instead, point it to the new get_source API endpoint on wrapdb.mesonbuild.com. This introduces a failure if wrapdb.mesonbuild.com goes down, but only in the fallback path when the canonical source URL is unavailable. That seems like a worthwhile trade for the added flexibility.

patch_url points to a redirect on wrapdb.mesonbuild.com, which is
convenient if we ever want to add additional mirrors or if we have to move
off of GitHub.  However, it also means wraps will fail to build if
wrapdb.mesonbuild.com goes down, unless the patch is already cached
locally.  Avoid this by adding a patch_fallback_url pointing directly to
the GitHub download.
source_fallback_url points directly at the source mirror in the GitHub
release, which means we can't retroactively add additional mirrors or move
existing releases off of GitHub.  Instead, point it to the new get_source
API endpoint on wrapdb.mesonbuild.com.  This (re-)introduces a failure
mode if wrapdb.mesonbuild.com goes down, but only in the fallback path
when the canonical source URL is unavailable.  That seems like a
worthwhile trade for the added flexibility.
@bgilbert
Copy link
Collaborator Author

bgilbert commented Nov 27, 2025

This requires the config changes in #2521 to be deployed.

Edit: done.

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