From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: chromium: update to 87.0.4280.66.
Date: Fri, 20 Nov 2020 00:28:24 +0100 [thread overview]
Message-ID: <20201119232824.9enC5ltZuG0_32sy6ThjdNoRhtxF9j47vQEeebXsN-E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26506@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
New comment by Logarithmus on void-packages repository
https://github.com/void-linux/void-packages/pull/26506#issuecomment-730699271
Comment:
Please, consider building it with my PR: https://github.com/void-linux/void-packages/pull/26144
Arch builds Chromium with PipeWire flag, and it works: https://github.com/archlinux/svntogit-packages/blob/packages/chromium/trunk/PKGBUILD
Fedora also uses it: https://src.fedoraproject.org/rpms/chromium/blob/master/f/chromium.spec#_1056
Also I've manually tested screen sharing on `x86_64-musl`, `x86_64` & `i686` with Chromium 86.
Having ability to share the screen on Wayland is a life-saver for me, especially in the light of remote working/studying.
P. S. Maybe it's better to split my PR into multiple separate PRs for each package?
next prev parent reply other threads:[~2020-11-19 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 17:55 [PR PATCH] " pbui
2020-11-19 18:30 ` q66
2020-11-19 23:21 ` Logarithmus
2020-11-19 23:28 ` Logarithmus [this message]
2020-11-20 0:58 ` pbui
2020-11-20 1:05 ` travankor
2020-11-20 1:24 ` Logarithmus
2020-11-20 2:09 ` q66
2020-11-20 2:10 ` [PR PATCH] [Merged]: " q66
2020-11-20 2:18 ` travankor
2020-11-20 2:18 ` travankor
2020-11-20 2:27 ` q66
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=20201119232824.9enC5ltZuG0_32sy6ThjdNoRhtxF9j47vQEeebXsN-E@z \
--to=logarithmus@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).