From: Achill Gilgenast <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 273e58: build: Allow systemd unit build without libsystemd
Date: Sun, 07 Dec 2025 18:58:49 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1031211/000000-273e58@github.com> (raw)
Branch: refs/heads/1031211
Home: https://github.com/bluez/bluez
Commit: 273e5838fd6010744b4325ca33135de2603b0705
https://github.com/bluez/bluez/commit/273e5838fd6010744b4325ca33135de2603b0705
Author: Achill Gilgenast <achill@achill.org>
Date: 2025-12-08 (Mon, 08 Dec 2025)
Changed paths:
M Makefile.am
M Makefile.mesh
M Makefile.obexd
M Makefile.tools
M configure.ac
Log Message:
-----------
build: Allow systemd unit build without libsystemd
Decouples libsystemd and systemd units from the same option and allows
installation of services without systemd.pc by manually specifying the
directories.
This is useful in Alpine Linux where we don't ship systemd, but allow
systemd services to be subpackaged for downstream distributions like
postmarketOS.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-12-08 2:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/1031211/000000-273e58@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox