-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
bluez: add tools to output that we were building anyway #39813
Conversation
Success on x86_64-linux (full log) Attempted: bluez Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: bluez Partial log (click to expand)
|
@@ -73,14 +76,21 @@ stdenv.mkDerivation rec { | |||
# Add extra configuration | |||
mkdir $out/etc/bluetooth | |||
ln -s /etc/bluetooth/main.conf $out/etc/bluetooth/main.conf | |||
|
|||
# Add missing tools, ref https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/bluez |
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.
This doesn't seem like something we should be doing- but I guess if Arch thinks its a good idea. Could you try doing this instead though:
substituteInPlace Makefile.tools --replace noinst_PROGRAMS bin_PROGRAMS
Not sure if it will work but IMO much cleaner than the for loop.
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.
This doesn't seem like something we should be doing
Why not? Some of these tools might be experimental but I fail to see why making them available is bad in any way. It's not a change of behaviour.
The substituteInPlace
didn't do the trick unfortunately (it would indeed have been much cleaner).
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.
I guess the main question is: why didn't the maintainers have these installed by default? It could just be a bug but there might also be a valid reason. Definitely not a blocker for this - I am just skeptical of custom install scripts in general.
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.
Based on my reading of the ML archives, the bluez guys deprecated the existing tools before having the replacements ready and while these tools are experimental, they are needed for certain tasks (example: toggle an adapter to LE mode only) that were previously the responsibility of hciconfig
and hcitool
.
The existence of them doesn't mean that the bluetooth daemon starts doing stuff differently so everything should work as normal but we now make low-level manipulation of the bluetooth stack/adapters possible again.
Success on aarch64-linux (full log) Attempted: bluez Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: bluez Partial log (click to expand)
|
Cc @andir |
Thanks for working on this (@peterhoeg). I am currently building things and running a nox-review over night. It looks pretty cleanish. As Matthew already mentioned I'll give it some verification during the coming day. I expect no major breakage since we are just adding a few files. |
It should be quite safe considering we're just adding a few binaries but not otherwise changing the build. |
@andir, you're good with this? |
@peterhoeg It looks alright. I didn't get to testing this so far. If you (both?) tested that I'm fine with it. |
My interest was in |
I backported it to my 18.03 laptop that I've with me and will try to test the bluetooth stuff once my rebuild is finished. |
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.
LGTM. I was able to pair with a new BT device.
Also the new tools seem to work for me.
Motivation for this change
A bunch of the old bluez tools have been deprecated (hciconfig, hcitool) but we weren't distributing their (experimental) replacements making certain bluetooth operations rather difficult.
This PR just adds in what we were building anyway (lifted from Arch Linux) + a few minor style cleanups.
Cc: @globin @fpletz
I haven't run nox-review as it wants to build the ~~~entire KDE suite~~~ a ton of packages.
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)