From: Bastien Nocera <hadess@hadess.net>
To: Funda Wang <fundawang@yeah.net>, linux-bluetooth@vger.kernel.org
Subject: Re: [Patch] support libical 4.0
Date: Mon, 11 May 2026 09:44:22 +0200 [thread overview]
Message-ID: <99b4c20de30a2991509b78db7751bd78044ad83d.camel@hadess.net> (raw)
In-Reply-To: <1445e90e.ded.19e159db7d2.Coremail.fundawang@yeah.net>
On Mon, 2026-05-11 at 13:58 +0800, Funda Wang wrote:
> Hello,
>
> Since libical 4.0 [1], pkgconfig files of libical have been splitted
> into several files according to libraries. The libical pkgconfig
> check need to be tweaked to check libicalvcal. Patch attached.
That breaks libical < 4.0, which is still the current version on most
stable distributions.
And please follow the instructions at:
https://github.com/bluez/bluez/blob/master/HACKING#L98
for how to send patches.
Regards
>
> Thanks.
>
> [1]: https://github.com/libical/libical/pull/988
next prev parent reply other threads:[~2026-05-11 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 5:58 [Patch] support libical 4.0 Funda Wang
2026-05-11 7:44 ` Bastien Nocera [this message]
2026-05-11 7:54 ` bluez.test.bot
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=99b4c20de30a2991509b78db7751bd78044ad83d.camel@hadess.net \
--to=hadess@hadess.net \
--cc=fundawang@yeah.net \
--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