Github messages for voidlinux
 help / color / mirror / Atom feed
From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: chromium: enable WebRTC screen sharing via PipeWire
Date: Sat, 21 Nov 2020 03:08:22 +0100	[thread overview]
Message-ID: <20201121020822.CfZ7Xe3k_CSqyymYLtiq65sS5pQ0XnJ1uICTnWW8PQI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26144@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

New comment by Logarithmus on void-packages repository

https://github.com/void-linux/void-packages/pull/26144#issuecomment-731490664

Comment:
> > That's because chromium's binary dlopens libpipewire, and libpipewire is missing in ldd /lib/chromium/chromium.
> > IMHO that's a bug in xbps.
> 
> That's all working as intended. Applications use `dlopen` exactly to allow for optional dependencies, and scanning a binary for what it does open will 1) be fragile and 2) remove the usefulness of dlopening in the first place.

OK, if I'll explicitly include `libpipewire0.2` into `depends` section, in addition to `makedepends`, will it finally work? 
IMHO the right solution to such problems is the support for optional dependencies `xbps`, like `pacman` does.
There's an issue about that https://github.com/void-linux/xbps/issues/1, but unfortunately `xbps` isn't actively developed anymore (I guess that's related to Juan RP's departure).

  parent reply	other threads:[~2020-11-21  2:08 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  3:49 [PR PATCH] chromium: enable Logarithmus
2020-11-05  4:25 ` [PR PATCH] [Updated] chromium: enable WebRTC screen sharing via PipeWire Logarithmus
2020-11-05  4:25 ` Logarithmus
2020-11-05  4:38 ` Logarithmus
2020-11-11  1:43 ` Logarithmus
2020-11-11  2:13 ` Logarithmus
2020-11-11  3:02 ` Logarithmus
2020-11-13 20:33 ` Logarithmus
2020-11-15  7:50 ` Logarithmus
2020-11-15 22:06 ` Logarithmus
2020-11-16  1:08 ` Logarithmus
2020-11-16  4:00 ` Logarithmus
2020-11-16  4:44 ` Logarithmus
2020-11-16 14:12 ` Logarithmus
2020-11-16 14:15 ` Logarithmus
2020-11-17 14:53 ` Logarithmus
2020-11-18  4:16 ` Logarithmus
2020-11-18  4:20 ` Logarithmus
2020-11-19  5:41 ` [PR PATCH] [Updated] " Logarithmus
2020-11-19 20:40 ` [PR PATCH] [Updated] [ci skip] chromium: update to 87.0.4280.66 & " Logarithmus
2020-11-19 21:54 ` Logarithmus
2020-11-20  1:02 ` [PR PATCH] [Updated] chromium: " Logarithmus
2020-11-20 21:26 ` Logarithmus
2020-11-21  0:59 ` [PR PATCH] [Updated] " Logarithmus
2020-11-21  1:00 ` Logarithmus
2020-11-21  1:03 ` ericonr
2020-11-21  1:15 ` [PR PATCH] [Updated] " Logarithmus
2020-11-21  1:35 ` Logarithmus
2020-11-21  1:46 ` Logarithmus
2020-11-21  1:53 ` Logarithmus
2020-11-21  1:54 ` Logarithmus
2020-11-21  1:54 ` Logarithmus
2020-11-21  1:57 ` Logarithmus
2020-11-21  1:57 ` Logarithmus
2020-11-21  1:57 ` Logarithmus
2020-11-21  1:59 ` Logarithmus
2020-11-21  2:00 ` ericonr
2020-11-21  2:08 ` Logarithmus
2020-11-21  2:08 ` Logarithmus [this message]
2020-11-21  2:08 ` Logarithmus
2020-11-21  2:10 ` Logarithmus
2020-11-21  2:28 ` [PR PATCH] [Updated] " Logarithmus
2020-11-21  2:29 ` Logarithmus
2020-11-21 11:17 ` ifreund
2020-11-21 11:44 ` Logarithmus
2020-11-21 11:44 ` Logarithmus
2020-11-21 12:33 ` ifreund
2020-11-21 12:34 ` ifreund
2020-11-21 13:21 ` Logarithmus
2020-11-21 13:22 ` Logarithmus
2020-11-21 13:23 ` Logarithmus
2020-11-21 19:04 ` ifreund
2020-11-22 14:52 ` ifreund
2020-12-03  7:10 ` [PR PATCH] [Updated] " Logarithmus
2020-12-13 21:42 ` [PR PATCH] [Closed]: " Logarithmus
2020-12-13 21:42 ` Logarithmus

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=20201121020822.CfZ7Xe3k_CSqyymYLtiq65sS5pQ0XnJ1uICTnWW8PQI@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).