-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat: check for gstreamer or pipewire libraries before setting them #24
base: main
Are you sure you want to change the base?
Conversation
@soumyaDghosh What is the problem that this patch fixes? In which cases can those variables be previously defined? |
In cases when the snap is building gstreamer or pipewire from and shipping within the snap, for eg, firefox, chromium, clapper |
@kenvandine I don't think I am the right person to review this |
This needs to be merged to fix https://launchpad.net/bugs/2074358. @jhenstridge or @sergio-costas, can you help reviewing this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Nathan commented, each environment variable should be checked independently.
9a45a96
to
831333e
Compare
This PR allows snaps to use their own set of pipewire or gstreamer libraries.
+1, thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, it makes sense.
@nteodosio I was doing some maintenance checks and found this awaiting for my approval... Is this still required? |
I'd say yes. I worked around it in Chromium, but this is sure to bite someone, somewhen if not merged. |
This PR allows snaps to use their own set of pipewire or gstreamer libraries.