Thomas Friedrichsmeier commented:
https://github.com/flathub/flathub/pull/3042
On hold for now, because executing binaries outside the sandbox fails due to
problems with the paths they see:
https://docs.flatpak.org/en/latest/sandbox-permissions.html (e.g. gcc would be
at /var/run/host/usr/bin, and can be started, but will fail as soon as it looks
for any other files in /usr; same for R).
Plan to work around this:
- Create a chroot-wrapper to start external R. The chroot dir (inside /app, I
guess) will have the standard paths mapped in.
- Start system-installed R inside that chroot.
- Whenever passing paths between frontend and backend, make sure to map them
as appropriate (this is going to be quite a hassle, but is a long-term-plan
anyway, in order to allow remote R backends, for instance).
- R will no longer be bundled inside the flatpak, after this, but be an
external dependency (if allowed)
---
For reference:
flatpak cheat-cheet: https://develop.kde.org/docs/build/flatpak/publishing/
--
Reply to this email directly or view it on GitLab:
https://invent.kde.org/education/rkward/-/issues/13#note_436361
You're receiving this email through KDE Activity Filter (see
sysadmin/activityfilter on invent.kde.org)
