-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
mixxx: 2.2.3 -> 2.2.4 #92482
mixxx: 2.2.3 -> 2.2.4 #92482
Conversation
Unfortunately I cannot test. |
According to comments in this commit mixxxdj/mixxx@9986605 the build system will use the internal copy if the system-wide libshout has higher version than 2.4.1. That means it does not make sense to try to use the system-wide 2.4.3 version, because it won't be used anyway. Otherwise ACK. |
Would it make sense to use our own libshout from a optimization-standpoint? Like,... less stuff compiled from the mixxx sources? |
That's exactly what is happening. Mixxx uses nix-built libshout, but the older version of it - 2.4.1. If we used newer version, it would be ignored during the build. |
So nothing to do here anymore, I guess... |
Just checked that streaming works with the systemwide libshout as an input (which the mixxx build recognizes as incompatible and uses internal copy instead). Advantage of this solution is that no action would be needed when libshout containing bugfix is released. Disadvantage is that it's less clear which version is used. |
Motivation for this change
https://github.com/mixxxdj/mixxx/releases/tag/release-2.2.4
Update bot skipped it:
@matthiasbeyer can you perhaps check if streaming works for you with the systemwide libshout version? It might, as release notes contain this line:
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)