site  contact  subhomenews

Chromium SFS uploaded

September 06, 2019 — BarryK

If you run PETget package manager (PPM), and install Chromium, it won't work. Easy has a script, /usr/local/petget/, that fixes some "difficult" packages. Chromium included, however the script is a bit old and needs updating for recent Chromiums.

I have updated the script, however, if you do install Chromium from PETget, you can perform a fix manually. Edit /usr/bin/chromium script, and alter the "exec" line to this:

     exec $LIBDIR/$APPNAME $CHROMIUM_FLAGS --test-type --no-sandbox "$@"

Then you should be good-to-go.

I have also created an SFS file. All SFSs for Easy Buster now require that you be running version 2.1.1 or later. Click "sfsget" on the desktop and you can install it, to run either in a container or on the main desktop.

So, now have some nice SFSs for Buster: Scribus, Krita and Chromium. What shall I add next?

It is not difficult to create these SFSs, except that Chromium involved a few hours work sorting out some details, such as default paths.
What I do is start with a "first bootup" situation, by erasing the session (see menu Filesystem -> Easy Version Control), then click on "petget" and install a package and it's dependencies, including any "doc" and "l10n" packages.
I then copy all of the '.session' folder somewhere, say: "cp -a /mnt/wkg/.session /mnt/sdc1/chromium_1.2.3_amd64"
I then delete all whiteout files: "find chromium_1.2.3_amd64  -mindepth 1 -type f -name '.wh.*' -delete" and some hidden files and folders at the top level.
I then go through and remove anything that isn't part of the Chromium install.
Maybe tweak a few things, such as the .desktop file, and make sure that usr/share/pixmaps/chromium.png exists, and for good measure usr/share/pixmaps/chromium48.png
I then run: "dir2sfs chromium_1.2.3_amd64"

If you want to try this for yourself, after creating the SFS, say 'myapp_1.2.3_amd64.sfs', copy it and myapp.specs and myapp.png, to /mnt/wkg/sfs/easyos/debian/buster, then click "sfsget" on the desktop and you can install it to a container ...and an icon should appear on the desktop.

One thing to be careful about, in usr/share/applications, make sure there is only one .desktop file, named appropriately, say 'myapp.desktop'. It is also highly recommended that "myapp" be the actual name of the executable. In future, I plan to support multiple .desktop files in the same SFS, but not yet.

In the future, all of the above could be automated and offered as an install option in PETget. That is, install to an SFS. 

Tags: easy