使用 Homebrew, apk, apt, dnf, Nix, pacman, zypper, MacPorts 安装 bluez

项目链接

• 主页
• 仓库
• 上游文档
• 软件包管理器页面

命令和别名

• bluemoon
• bluetoothctl
• btattach
• btmon
• hex2hcd
• isotest
• l2ping
• l2test
• mpris-proxy
• rctest

项目历史

The BlueZ project has long been published from the Linux kernel infrastructure, with its canonical source repository hosted under git.kernel.org's bluetooth namespace and identified there as the Bluetooth protocol stack for Linux.

BlueZ evolved alongside Linux Bluetooth support: early releases exposed separate tools and profile helpers, while later releases centered the stack on bluetoothd, D-Bus APIs, and kernel/user-space cooperation for controllers, pairing, audio, input, and low-energy devices.

The BlueZ 4 series began in August 2008 and BlueZ 5 followed in December 2012, both visible in the official git.kernel.org tag history as major line changes in the Linux Bluetooth user-space stack.

采用历史

BlueZ became the default Bluetooth stack carried by Linux distributions because it is the upstream implementation for the Linux Bluetooth ecosystem, not just a third-party command-line utility.

Its adoption is visible in package managers: the same project is shipped by Homebrew, Debian/Ubuntu, Fedora, Arch, Alpine, openSUSE, Nix, and MacPorts, often split by distributions into daemons, libraries, tools, and compatibility packages.

The project also shaped desktop and embedded Linux Bluetooth usage. GNOME-facing bluez-gnome work tracked the BlueZ 4 D-Bus API transition, while embedded guides commonly build directly from the kernel.org BlueZ tarballs for board bring-up.

使用方式

Package users usually meet BlueZ through bluetoothd, bluetoothctl, btmon, btattach, l2ping, and related diagnostic tools. It is used for pairing devices, attaching HCI controllers, inspecting traffic, testing L2CAP/RFCOMM behavior, and running profile support.

On Linux systems, BlueZ is configured through files such as /etc/bluetooth/main.conf and integrated with system services, udev, D-Bus, PulseAudio/PipeWire, NetworkManager, and desktop Bluetooth front ends.

为什么软件包爱好者会关心

BlueZ is package-nerd-important because it sits at the boundary where kernel interfaces, D-Bus APIs, firmware quirks, Bluetooth qualification, desktop UX, audio stacks, and security patches all collide.

It is also a classic distro-maintainer package: upstream releases may affect controllers, headphones, keyboards, low-energy devices, mesh tooling, audio profiles, and security posture, so downstreams often carry patches while tracking upstream closely.

For Homebrew specifically, bluez is unusual because it brings Linux Bluetooth tooling to a macOS package manager even though the core stack is Linux-native; the formula is most useful for development, diagnostics, and cross-platform tooling rather than replacing Apple's Bluetooth stack.

时间线

• 2000s: BlueZ becomes the Linux Bluetooth user-space stack hosted in the kernel.org Bluetooth source area.
• 2008-08: BlueZ 4.0 is tagged in the official git.kernel.org repository.
• 2012-12: BlueZ 5.0 is tagged in the official git.kernel.org repository.
• 2010s-2020s: BlueZ remains hosted under git.kernel.org and distributed across mainstream Linux package managers.

Related projects

• Linux kernel Bluetooth subsystem: the in-kernel protocols and HCI drivers BlueZ controls from user space.
• bluetoothd and bluetoothctl: the central daemon and interactive control CLI shipped by BlueZ.
• btmon and hcidump: packet monitoring and historical diagnostic tooling around Linux Bluetooth.
• PulseAudio and PipeWire: Linux audio stacks that depend on BlueZ integration for Bluetooth audio devices.
• GNOME Bluetooth and other desktop front ends: user interfaces built on top of BlueZ's D-Bus APIs.

来源

• https://git.kernel.org/pub/scm/bluetooth/bluez.git/refs/tags
• https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/README
• https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc
• source_facts.package-manager