-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent building a wheel if BUILD_AGAINST_ALL_FFMPEG_FROM_S3 is not set #31
Prevent building a wheel if BUILD_AGAINST_ALL_FFMPEG_FROM_S3 is not set #31
Conversation
@NicolasHug has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@NicolasHug has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
1 similar comment
@NicolasHug has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@NicolasHug has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@NicolasHug has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
…t_wheel_building_against_single_ffmpeg
@NicolasHug has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@NicolasHug merged this pull request in e1e0352. |
When we build a wheel (typically in preparation of a new release), we should always build against our non-GPL FFmpeg libraries on S3, i.e.
BUILD_AGAINST_ALL_FFMPEG_FROM_S3
should be set. This PR enforces that, and should prevent us from pushing a problematic wheel on PyPI.There might be good reasons to build a wheel against a specific installed version (e.g. maybe internally, or for debugging, or for an esoteric local setup). We still allow that if
I_SWEAR_I_KNOW_WHAT_IM_DOING
is set (happy to consider other names...)