The new skip for the dynamic linker introduced in
ccfd26ef14ea ("bintools-wrapper: skip dynamic linker for static
binaries") includes a change in behaviour, previously the $link32
variable was checked using an arithmetic expression via (( )). This
returns zero if the output of the arithmetic expression is nonzero, i.e.
link32=1 would return zero and the if condition would be executed.
The code refactored this to use "$link32" = "0" which is incorrect in
this case, since we want this if conditional to run if $link32 is 1.
Small shell excerpt for clarity:
$ export link32=1
$ export cookie=1
$ if [[ "$cookie" = "1" ]] && (( "$link32" )); then echo "do some stuff"; fi;
do some stuff
$ if [[ "$cookie" = "1" && "$link32" = "0" ]]; then echo "do some stuff"; fi;
$
Change it to check for $link32 = "1", as the previous code did.
It was restricted in 40b347f2051b158e4d077eb95eff02df8a65524f due to its
need for the SSE2 instruction set. However the upstream issue is now
resolved [1], so reenable support for all platforms.
[1] https://github.com/chrjguill/i3lock-color/issues/44
The desktop item was referring to "$out/bin/xonotic" as executable, but
since it's built in its own derivation now, "$out" did not contain the
xonotic wrapper.
Since it seems to be common practise to use a relative path, I changed
it to do that here as well.
As @lopsided98 points out in #105305, since the hashes are now target
sensative, and until we find reason to actually care to test what they
are exactly, we are best just normalizing them away in the tests.
Since people regularly open reports about tracker search not working because
python is not found.
And since Tracker Search in qBittorrent can not be disabled & at the same time
the Pythong is needed for it to work - including Python for default
functionality to work.
The top-level "wayfire" attribute is a Wayfire with wf-shell installed
and nothing else. But wayfireApplications.withPlugins can be used to
create a Wayfire with arbitrary plugins, or no plugins at all.
