From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: google-chrome: don't depend on qt5-{core,gui,widgets}
Date: Mon, 31 Oct 2022 13:30:07 +0100 [thread overview]
Message-ID: <20221031123007.6oo5vuCrVqtp2i2SAUrayaR6W_mOc42OqkpCHc2LqGw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40239@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]
There's a merged pull request on the void-packages repository
google-chrome: don't depend on qt5-{core,gui,widgets}
https://github.com/void-linux/void-packages/pull/40239
Description:
#### Testing the changes
- I tested the changes in this PR: **YES** (on a machine without any `qt5*` packages)
---
This disables rdep scanning for `libqt5_shim.so`, as does upstream:
https://chromium.googlesource.com/chromium/src/+/8fcee9b26219683fb20bc51826629cac2e3584a0%5E%21/#F0
Otherwise it pulls in `qt5-widgets`, etc.:
```
# xbps-install -R . google-chrome
Name Action Version New version Download size
double-conversion install - 3.1.5_1 29KB
qt5-core install - 5.15.5+20220728_1 2408KB
libevdev install - 1.12.0_1 38KB
libwacom install - 1.12_1 92KB
mtdev install - 1.1.6_1 12KB
libinput install - 1.21.0_1 253KB
libxkbcommon-x11 install - 1.4.1_1 13KB
qt5-dbus install - 5.15.5+20220728_1 194KB
qt5-network install - 5.15.5+20220728_1 692KB
tslib install - 1.22_1 50KB
xcb-util-image install - 0.4.0_3 9436B
xcb-util-renderutil install - 0.3.9_3 7632B
qt5-gui install - 5.15.5+20220728_1 3935KB
qt5-widgets install - 5.15.5+20220728_1 2587KB
google-chrome update 106.0.5249.119_1 107.0.5304.87_1 -
Size to download: 10MB
Size required on disk: 321MB
Space available on disk: 112GB
```
Maintainer ping: @atk
prev parent reply other threads:[~2022-10-31 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 9:18 [PR PATCH] " mvf
2022-10-31 9:26 ` atk
2022-10-31 12:30 ` sgn [this message]
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=20221031123007.6oo5vuCrVqtp2i2SAUrayaR6W_mOc42OqkpCHc2LqGw@z \
--to=sgn@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).