You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To provide snapcraft-like features (like the ability to install betterSIS via GUI and keeping it up to date) to a more broad userbase betterSIS should also be released as a Flatpak.
snapcraft targets primarily Ubuntu users.
The major obstacle is to allow SIS to find files that are placed inside an hardcoded path:
/usr/local/share/sis
A possible solution that I've found is to use proot: thanks to the -b flag it is possible to "redirect" SIS from the hardcoded path to a custom path which is inside the flatpak container.
From the proot wiki:
The bind mechanism enables one to relocate files and directories. This is typically useful to trick programs that perform access to hard-coded locations, like some installation scripts
To verify that it works I have copied the files from /usr/local/share/sis inside a folder, redirected SIS to that folder and launching the source script.rugged command. I have then tried to redirect /usr/local/share/sis to a folder that does NOT have SIS files and the source script.rugged command returns a message "file not found".
So the simple solution is to package proot inside the container and use it to execute SIS...
Does calling proot on betterSIS work? Or it must be called on SIS itself? If it only works on SIS then the siswrapper library might need changes to allow the execution of SIS using proot
... But proot is GPL-2 licensed and I don't know if this means that betterSIS must also be GPL licensed.
From what I've found online it seems like distributing a non-modified binary protected by GPL inside a container together with an application that doesn't include the GPL source code is allowed but I'm not sure.
For example I've found people distributing the ffmpeg and pandoc binaries with their application without any issue.
The text was updated successfully, but these errors were encountered:
To provide snapcraft-like features (like the ability to install betterSIS via GUI and keeping it up to date) to a more broad userbase betterSIS should also be released as a Flatpak.
The major obstacle is to allow SIS to find files that are placed inside an hardcoded path:
A possible solution that I've found is to use proot: thanks to the
-b
flag it is possible to "redirect" SIS from the hardcoded path to a custom path which is inside the flatpak container.From the proot wiki:
I tried it very briefly using this command and it seems to work:
So the simple solution is to package proot inside the container and use it to execute SIS...
... But proot is GPL-2 licensed and I don't know if this means that betterSIS must also be GPL licensed.
From what I've found online it seems like distributing a non-modified binary protected by GPL inside a container together with an application that doesn't include the GPL source code is allowed but I'm not sure.
The text was updated successfully, but these errors were encountered: