Edit 08/01/22: See this post, viewtopic.php?p=63387#p63387
Consider this a ‘Proof of Concept’. Feedback by others would be appreciated. See the last paragraph.
I had recalled that someone had posted about supplying 'missing libs' so that one of MikeWalsh's portables could be run under some 64-bit Slacko. I had hoped to find that post identifying such libs and perhaps supplying them. But my search only revealed that under a version of Iron64-portable libpng12 and perhaps (& perhaps a different post) libpcre.so.3 were missing. I've attached those as they will be needed.
I first tried to start Brave via a terminal. Opening halted; the terminal reporting that libatk-bridge-2.0.so.0 was not found. Examining the binaries used in all MikeWalsh's portable Chrome & 'Chromium Clones' from ScPup64 with ListDD revealed these 'missing' libs, libatk-bridge-2.0.so.0, libatspi.so.0. But 'ldding' Slimjet's binary in addition to those also reported libgtk-3.so.0 and libgdk-3.so.0 'missing'.
libatk-bridge-2.0.so.0, libatspi.so.0 are, in fact, included in MikeWalsh’s package, in a sub-folder named lib. So they are present; but not being used. After trying other methods, it finally occurred to me to see if modification of the LAUNCH script ala fredx181’s ‘ff’ under firefox would work. So I edited the Brave-portable64’s LAUNCH SCRIPT by adding the lines in blue to read:
#!/bin/sh
#
# Launcher for 'portable' Brave browser
#
HERE="$(dirname "$(readlink -f "$0")")"
#
LAUNCHDIR="$(cd "$(dirname "$0")"; pwd)"
LAUNCHDIR="$(dirname "$(readlink -f "$0")")"
LD_LIBRARY_PATH=$LAUNCHDIR/:$LAUNCHDIR/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
mkdir "$HERE/PROFILE" 2> /dev/null
mkdir "$HERE/PROFILE/spot" 2> /dev/null
mkdir "$HERE/PROFILE/spot/Brave-Browser" 2> /dev/null
#
chown -R spot:spot "$HERE/brave"
chown -R spot:spot "$HERE/lib"
chown -R spot:spot "$HERE/PROFILE/spot"
#
if grep -q 'Quirky April64' /etc/DISTRO_SPECS
then
LD_LIBRARY_PATH=$HERE/:$HERE/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
run-as-spot "$HERE/brave/brave" --user-data-dir=$HERE/PROFILE/spot/Brave-Browser --disk-cache-size=5000000 --media-cache-size=5000000 --allow-outdated-plugins "$@"
else
run-as-spot "$HERE/brave/brave" --user-data-dir=$HERE/PROFILE/spot/Brave-Browser --disk-cache-size=5000000 --media-cache-size=5000000 --allow-outdated-plugins "$@"
fi
After adding later versions and symlinks respectively named libpng12 and libpcre.so.3 to the ‘lib’ folder, Brave-portable64 opened via the edited LAUNCH script. But not without complaining of some errors.
Whether those or otherwise one error seems to be significant. Attempting to attach the aforementioned file to this post didn’t work.
So although the text of this post is from the aforesaid Brave, I've had to open a different Web-browser to provide the attachment.
Scripting isn’t my forte. The lines I flinched from firefox could be edited to make better use of the declarations MikeWalsh used in the LAUNCH script. Actually, now that I've looked at the modified script I don't know why the modification was (a) needed and (b) worked. The original already had a provision for using the files found in 'lib'. I wonder if it's a 'timing' thing? the use of file in the 'lib' folder commanded before that folder is converted to spot permissions.
I haven’t yet had time to try this technique with Google-Chrome and other of MikeWalsh’s portables. And I don't have other Slacko64s setup to boot into. It’s likely that appropriate files relating to libgtk-3.so.0 and libgdk-3.so.0 will also have to be added to the ‘lib’ folder in order for slimjet to run. [Edit: visual examination revealed those libraries present in Slimjet-portables LIB subfolder]. So consider this a ‘Proof of Concept’.
