From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qutebrowser: disable webengine build option where it's broken
Date: Mon, 13 Jul 2020 21:08:08 +0200 [thread overview]
Message-ID: <20200713190808.VyjkTxdYPjZ55hJAQVeiJonHQd8scewaWeTuZPdzZfY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23546@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/23546#issuecomment-657738441
Comment:
After a closer look at `python*-PyQt5-webengine` and a comment from @Johnnynator, I realized that the file-based configuration mechanism for `python*-PyQt5-webengine` is broken and cross builds are simply not possible. This masqueraded as an `aarch64` problem because those are the only architectures CI and the builders cross-compile that wasn't already broken for other reasons. I don't think this is worth fixing at least until PyQt5 5.15 can be packaged (which brings its own challenges), so I'm marking `nocross` for now.
To allow an up-to-date `qutebrowser` on those architectures where `python*-PyQt5-webengine` is no longer available, I've disabled the `webengine` default build option for cross builds.
cc: @Chocimier
next prev parent reply other threads:[~2020-07-13 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 16:58 [PR PATCH] " ahesford
2020-07-13 18:54 ` [PR PATCH] [Updated] " ahesford
2020-07-13 19:08 ` ahesford [this message]
2020-07-13 19:18 ` [PR REVIEW] " Chocimier
2020-07-13 19:29 ` [PR PATCH] [Updated] " ahesford
2020-07-13 19:31 ` [PR REVIEW] " ahesford
2020-07-13 20:17 ` [PR PATCH] [Merged]: " 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=20200713190808.VyjkTxdYPjZ55hJAQVeiJonHQd8scewaWeTuZPdzZfY@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).