From: pbui <pbui@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: chromium: update to 87.0.4280.88.
Date: Sat, 12 Dec 2020 21:35:36 +0100 [thread overview]
Message-ID: <20201212203536.bbSl_gvt8cRocvQbi9SgJAgElzXtok_t0kP11xd0JPc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27060@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
New comment by pbui on void-packages repository
https://github.com/void-linux/void-packages/pull/27060#issuecomment-743838145
Comment:
@Logarithmus @ifreund I was able to build the version of chromium with the pipewire build option on, but when I go to install it, xbps does not require libpipewire0.2 as a dependency.
Checking `ldd` on `/usr/lib/chromium/chromium` shows that the executable does not depend on `libpipewire`... did I do something wrong or is this expected? I can run my rebuilt chromium without libpipewire0.2 installed.
In the meantime, I am building musl now...
next prev parent reply other threads:[~2020-12-12 20:35 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 1:45 [PR PATCH] " pbui
2020-12-12 14:36 ` ericonr
2020-12-12 15:03 ` pbui
2020-12-12 15:55 ` Logarithmus
2020-12-12 15:56 ` Logarithmus
2020-12-12 15:58 ` Logarithmus
2020-12-12 16:00 ` Logarithmus
2020-12-12 16:02 ` Logarithmus
2020-12-12 16:06 ` pbui
2020-12-12 16:07 ` Logarithmus
2020-12-12 16:14 ` Logarithmus
2020-12-12 16:47 ` pbui
2020-12-12 16:53 ` Logarithmus
2020-12-12 16:55 ` ifreund
2020-12-12 16:58 ` Logarithmus
2020-12-12 20:35 ` pbui [this message]
2020-12-12 20:47 ` ifreund
2020-12-12 20:50 ` [PR PATCH] [Updated] " pbui
2020-12-12 20:51 ` Logarithmus
2020-12-12 20:55 ` [PR REVIEW] " ericonr
2020-12-12 20:55 ` Logarithmus
2020-12-12 20:55 ` Logarithmus
2020-12-12 20:57 ` pbui
2020-12-12 20:57 ` Logarithmus
2020-12-12 20:58 ` Logarithmus
2020-12-12 20:59 ` [PR PATCH] [Updated] " pbui
2020-12-12 20:59 ` [PR REVIEW] " Logarithmus
2020-12-12 21:00 ` pbui
2020-12-12 23:06 ` pbui
2020-12-12 23:08 ` Logarithmus
2020-12-12 23:20 ` pbui
2020-12-12 23:40 ` Logarithmus
2020-12-12 23:41 ` Logarithmus
2020-12-13 1:13 ` ericonr
2020-12-13 1:15 ` [PR REVIEW] " ericonr
2020-12-13 1:18 ` ericonr
2020-12-13 2:54 ` [PR PATCH] [Updated] " pbui
2020-12-13 2:55 ` pbui
2020-12-13 5:47 ` [PR REVIEW] " ericonr
2020-12-13 9:00 ` Logarithmus
2020-12-13 12:08 ` Logarithmus
2020-12-13 14:10 ` [PR REVIEW] " pbui
2020-12-13 14:12 ` [PR PATCH] [Updated] " pbui
2020-12-13 21:28 ` [PR PATCH] [Merged]: " ericonr
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=20201212203536.bbSl_gvt8cRocvQbi9SgJAgElzXtok_t0kP11xd0JPc@z \
--to=pbui@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).