@MochiMoppel :-
Hm. O-kayyy....
I LIKE that! That looks so much neater & tidier, and.....it works, really well. So; this is the wrapper-script as it now stands. I'm all for simplification wherever possible:-
Code: Select all
#!/bin/sh
# Launcher for 'portable' Opera browser
#
export HERE="$(dirname "$(readlink -f "$0")")"
tee "$HERE"/opera/resources/ffmpeg_preload_config.json >/dev/null <<EOF
[
"${HERE}/opera/lib_extra/libffmpeg.so"
]
EOF
#
mkdir -p /opt/google/chrome
ln -s $HERE/opera/WidevineCdm /opt/google/chrome/WidevineCdm
#
mkdir -p "$HERE/PROFILE"
#
grep -Eq 'puppy_tahr64|puppy_xenialpup64' /etc/os-release && LD_LIBRARY_PATH=$HERE/:$HERE/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
"$HERE/opera/opera" --user-data-dir=$HERE/PROFILE --enable-features=VaapiVideoDecoder --start-maximized --disable-infobars --force-device-scale-factor=1.3 --no-sandbox "$@"
#
rm -rf /opt/google
Some of the code can't really be changed. Seaside's tee stuff is necessary for auto-location of libffmpeg, since the Opera devs have hard-coded the thing, at build-time, to look for it in a very specific location.....and between us we found that the way seaside put that together was the ONLY workaround that was functional for us here in Puppyland!
As for the "--switch" options; mm. Thinking about it now, the --VaapiVideoDecoder is probably non-functional for most people. dimkr expounded on this point at length a while back when he was justifying WHY his Vanilla DPup was somewhat larger than some people were happy with. For modern systems to function AND perform the way folks expect today, a certain amount of additional Xorg & Mesa/OpenGL items need to be included.....and of course, you add things in, they ARE going to occupy more space. His reply was that the addition of this "extra" stuff will, in the long run, actually make life easier for the graphics sub-systems even on older hardware, despite that there's more code for them to run through.....because it will switch-in existing functionality that has largely been ignored by many devs over the years.
Since Puppy is still, even today, intended to keep older hardware useful AND give it a fighting chance of coping with increasing hardware demands, anything like this has got to be considered.
I "borrowed" that particular "--switch" from 'Marmaduke's' Ungoogled Chromium builds.....before I understood that he'd included the software that enables all this into his builds at compile time. I've been meaning to remove that "switch" for a while now; I guess this is as good a time as any, since it needs the matching system software to truly function as it should.....and most Puppies just don't have it.
===================================
A question, if I may? I've reached the stage where I know what 'pipes' do, and I understand what a single ampersand ("&") does in scripting; what does the double ampersand actually do? I've seen it used in various scripts a lot over the years, but I still don't really comprehend what it does...especially here. Does the second one 'reinforce' what the first one is doing, or what, exactly?
Mike. 