unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Sarah Morgensen" <iskarian@mgsn.dev>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, 34135@debbugs.gnu.org
Subject: bug#34135: IceCat lacks WebGL support
Date: Sun, 26 Sep 2021 05:50:18 -0400	[thread overview]
Message-ID: <87h7e7ekcq.fsf@netris.org> (raw)
In-Reply-To: <86y27kureb.fsf@mgsn.dev>

Hi Sarah,

Thanks for looking into this, and more generally for all the work you've
been putting into Guix lately.

Sarah Morgensen <iskarian@mgsn.dev> writes:
> While it looks like preliminary precise whitelisting was done for
> ffmpeg, it seems that this approach may require excessive effort for
> WebGL.

Perhaps, but I don't think that's yet been established.

For what it's worth, as the maintainer of our IceCat package since the
early years of Guix, I'm uncomfortable allowing the IceCat sandbox to
obtain a complete list of software (with precise versions) installed on
our users' systems.  I hope that we will not give up so easily on
precise whitelisting.

> For example, after whitelisting libxcb,
> it needs
>
>   /gnu/store/w68jrgqqbfcakm27wm4zf7hmpgw294my-libxxf86vm-1.1.4/lib/libXxf86vm.so.1
>
> and after whitelisting that one,
>
>   /gnu/store/jwga98k68l0h5c45jx7z4jdjzhfc34vm-libxshmfence-1.3/lib/libxshmfence.so.1
>
> and so on.

I agree that this approach would be very tedious, but there are better
ways.  I faced a similar problem before I wrote the existing precise
whitelisting code (which your proposed patch would remove): 'libavcodec'
had too many dependencies, and I didn't want to maintain a list of them
all.  I eventually realized that 'libavcodec's RUNPATH would cover most
of what was needed, and in fact only one additional directory needed to
be added manually.

Would you like to try adding the RUNPATHs of Mesa's libraries to the
whitelist, i.e. using the same code that computes 'libavcodec-runpath'?

To find the directories that must be added manually, how about scraping
the *successful* log for a list of file names in /gnu/store and
distilling it down to a set of packages?

> Both the above are propagated-inputs in mesa.  So, it seems
> to "properly" fix this, we would need to read *all* input libraries
> recursively.

Even if we had to do that, it wouldn't be an excessive amount of effort.
We already have the code to extract the RUNPATH of a library and add it
to the whitelist.  Doing that for all libraries found in FOO/lib/*.so
for all inputs FOO shouldn't be much harder, no?

What do you think?  Would you like to try it?

    Regards,
      Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.




  reply	other threads:[~2021-09-26  9:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19 15:49 bug#34135: IceCat lacks WebGL support Ludovic Courtès
2019-01-19 17:07 ` Julien Lepiller
2019-01-20 22:45   ` Ludovic Courtès
2019-01-21  8:24     ` Ricardo Wurmus
2019-01-21  8:49       ` Julien Lepiller
2019-01-21  9:54         ` Ludovic Courtès
2019-01-21 14:12           ` Ricardo Wurmus
2021-09-26  0:11           ` Sarah Morgensen
2021-09-26  9:50             ` Mark H Weaver [this message]
2020-05-12 18:19 ` Jonathan Brielmaier
2020-05-17 20:24 ` Jonathan Brielmaier
2020-05-23 21:14   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-05-23 22:02     ` Jonathan Brielmaier
2020-05-17 20:44 ` Jonathan Brielmaier
2023-08-29 20:48 ` Maxim Cournoyer
2023-09-09 10:52   ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7e7ekcq.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=34135@debbugs.gnu.org \
    --cc=iskarian@mgsn.dev \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).