From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libxkbcommon: update to 1.0.1.
Date: Wed, 30 Sep 2020 03:29:52 +0200 [thread overview]
Message-ID: <20200930012952.3i_2Bd3jgYqhIdLJyoPVu6H9b81LOJJqjlZRhUcJLdk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25134@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/25134#issuecomment-701105750
Comment:
OK, I pushed some changes to your branch. The new `libxkbcommon` builds some command-line tools that, in your PR, added Wayland and X11 dependencies that caused the problem you observed. To get around this, I moved the tools into a new `libxkbcommon-tools` subpackage so these dependencies are not attached to the `libxkbcommon` base package. I have successfully built `wlroots`, `i3lock`, `wev`, `kitty` and `rofi` on `x86_64`. We should be OK now.
Finally, the xkbregistry library is optional and, since we obviously have nothing that depends on it, I've just disabled it during the build. We can enable it in a subsequent build if a package needs it.
If you accept these changes, let me know; I will squash and merge. Otherwise, feel free to make an alternative suggestion.
next prev parent reply other threads:[~2020-09-30 1:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 17:12 [PR PATCH] " dashezup
2020-09-27 18:19 ` [PR PATCH] [Updated] " dashezup
2020-09-29 14:08 ` ahesford
2020-09-29 20:59 ` [PR PATCH] [Updated] " dashezup
2020-09-29 21:26 ` dashezup
2020-09-29 21:55 ` dashezup
2020-09-29 21:55 ` dashezup
2020-09-29 21:56 ` [PR PATCH] [Updated] " dashezup
2020-09-29 22:12 ` dashezup
2020-09-29 22:12 ` dashezup
2020-09-29 22:42 ` dashezup
2020-09-30 1:24 ` [PR PATCH] [Updated] " ahesford
2020-09-30 1:29 ` ahesford [this message]
2020-09-30 9:48 ` dashezup
2020-09-30 12:39 ` [PR PATCH] [Closed]: " 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=20200930012952.3i_2Bd3jgYqhIdLJyoPVu6H9b81LOJJqjlZRhUcJLdk@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).