From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Abhishek Cherath <abhi@quic.us>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
69971@debbugs.gnu.org, Vivien Kraus <vivien@planete-kraus.eu>
Subject: [bug#69971] [PATCH v2] gnu: webkitgtk: Add locale and dri access to gtk sandbox in order to silence gtk locale warnings and enable hardware accelerated video, respectively.
Date: Mon, 01 Apr 2024 08:32:04 +0200 [thread overview]
Message-ID: <9b96d46745090dfb5c1154c74f56ca9d57440908.camel@gmail.com> (raw)
In-Reply-To: <E983C543-DFB0-4BA6-BCE2-9DEF3955D7EC@quic.us>
Am Sonntag, dem 31.03.2024 um 22:17 -0400 schrieb Abhishek Cherath:
> It was a conservative choice, but not made for security reasons, I'm
> just not sure where and how this wrapper runs, and I was mildly tired
> of recompiling webkitgtk.
>
> I'm not opposed to having it be $HOME, if that works; I don't see
> what security issues there could be.
I think dynamic choices should be possible – IIRC, std::strings are
used for arguments, but even if not, we're dealing with C++, so we can
allocate "on the stack".
Am Sonntag, dem 31.03.2024 um 21:33 -0400 schrieb Maxim Cournoyer:
> Liliana, I remember you would prefer not having webkitgtk changes
> happen on master; do you have a suggestion of which branch this
> should be committed to? gnome-team?
We can do this on gnome-team, we still have some leftover world
rebuilds from 44.10. I'd prefer if stuff that rebuilds webkitgtk on
master were grafted, as it causes more than the prescribed 300 rebuilds
and is a nasty build itself.
Cheers
next prev parent reply other threads:[~2024-04-01 6:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 2:02 [bug#69971] [PATCH] gnu: webkitgtk: Add locale and dri access to gtk sandbox in order to silence gtk locale warnings and enable hardware accelerated video, respectively Abhishek Cherath
2024-03-24 5:54 ` [bug#69971] [PATCH v2] " Abhishek Cherath
2024-04-01 1:33 ` Maxim Cournoyer
2024-04-01 2:17 ` Abhishek Cherath
2024-04-01 6:32 ` Liliana Marie Prikler [this message]
2024-04-01 10:49 ` Abhishek Cherath
2024-04-01 17:05 ` Liliana Marie Prikler
2024-04-01 18:11 ` Jack Hill
2024-04-01 18:20 ` Liliana Marie Prikler
2024-04-01 18:28 ` Abhishek Cherath
2024-03-24 6:24 ` [bug#69971] Explanation Abhishek Cherath
2024-03-24 21:22 ` [bug#69971] Some more information Abhishek Cherath
2024-03-24 21:26 ` Abhishek Cherath
2024-04-18 3:09 ` [bug#69971] Submitted to gnome-team Abhishek Cherath
2024-04-18 3:14 ` [bug#69971] close 69971 Abhishek Cherath
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=9b96d46745090dfb5c1154c74f56ca9d57440908.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=69971@debbugs.gnu.org \
--cc=abhi@quic.us \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/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).