From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: astroid: build with guri and webkit2gtk-4.1
Date: Sat, 02 Mar 2024 10:37:19 +0100 [thread overview]
Message-ID: <20240302093719.B88022470E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49013@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/49013#issuecomment-1974746222
Comment:
> Is this about getting rid of old dependencies in the ecosystem from a Void perspective?
webkit2gtk is a massive dependency and having to compile it 3 times is not ideal. Many distros have already stopped shipping webkit2gtk-4.0 and the changes in this case are relatively simple. (the guri changes are necessary since libsoup2 and libsoup3 cannot be loaded in the same process at the same time, and libsoup3 removed the SoupUri api)
> I generally think though that changes should be integrated upstream as often as possible.
Of course, that is why I submitted a PR upstream and this is marked as a draft.
next prev parent reply other threads:[~2024-03-02 9:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 23:15 [PR PATCH] " oreo639
2024-03-01 17:51 ` bitmeise
2024-03-01 21:32 ` [PR PATCH] [Updated] " oreo639
2024-03-01 21:33 ` oreo639
2024-03-01 21:34 ` oreo639
2024-03-01 21:46 ` oreo639
2024-03-02 9:15 ` bitmeise
2024-03-02 9:33 ` oreo639
2024-03-02 9:33 ` oreo639
2024-03-02 9:34 ` oreo639
2024-03-02 9:35 ` oreo639
2024-03-02 9:37 ` oreo639 [this message]
2024-06-01 1:50 ` github-actions
2024-06-01 8:31 ` oreo639
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=20240302093719.B88022470E@inbox.vuxu.org \
--to=oreo639@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).