From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3: enable bluetooth sockets
Date: Wed, 13 Apr 2022 15:34:30 +0200 [thread overview]
Message-ID: <20220413133430.RqeoDIZ-56P6l2VhIa_L6gozbSnctzeh7VvtPNIx3QE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36640@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/36640#issuecomment-1098058183
Comment:
I don't think we should vender these headers here. My hope was that kernel-libc-headers would be easy to modify to add those headers, but looking through the kernel headers has convinced me that we don't want the trouble.
I think you should drop the most recent two commits and go back to pulling in `libbluetooth-devel` in `python3` and breaking the (default) cycle in `bluez`.
next prev parent reply other threads:[~2022-04-13 13:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 19:10 [PR PATCH] " tornaria
2022-04-11 19:31 ` paper42
2022-04-11 19:32 ` paper42
2022-04-11 20:20 ` [PR PATCH] [Updated] " tornaria
2022-04-11 20:36 ` tornaria
2022-04-12 4:33 ` classabbyamp
2022-04-12 21:33 ` tornaria
2022-04-12 23:01 ` ahesford
2022-04-12 23:01 ` ahesford
2022-04-13 4:21 ` [PR PATCH] [Updated] " tornaria
2022-04-13 13:34 ` ahesford [this message]
2022-04-13 15:22 ` tornaria
2022-04-13 15:57 ` [PR PATCH] [Updated] " tornaria
2022-04-13 16:11 ` tornaria
2022-04-14 15:56 ` ahesford
2022-06-08 2:08 ` ahesford
2022-09-06 2:16 ` github-actions
2022-09-06 2:19 ` classabbyamp
2022-09-18 19:46 ` [PR PATCH] [Closed]: " ahesford
2022-09-18 19:46 ` ahesford
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=20220413133430.RqeoDIZ-56P6l2VhIa_L6gozbSnctzeh7VvtPNIx3QE@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).