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
libwacom: 0.29 -> 0.31 #48381
libwacom: 0.29 -> 0.31 #48381
Conversation
@infinisil brought up a good argument for building from the repository source instead of using the release tarball. This way, we are not dependent on this exact source. Therefore, I've changed it to use |
I guess this is a mass-rebuild with similar impact as #48434. Should it be merged into |
Yes, please. |
8ee70a5
to
d584520
Compare
Success on aarch64-linux (full log) Attempted: libwacom Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: libwacom Partial log (click to expand)
|
Motivation for this change
Upgrade libwacom. Also, changed the mirror from SourceForge to GitHub. (As requested in #48209)
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)This uses
fetchurl
and takes the release package (.tar.bz2
), as the release-commit differs slightly:I'm guessing most of these files could be generated by using the
autoreconfHook
. Is it better to take the release tarball or try using the source withfetchGitHub
?