Please read : Important information about the Chromium-based 'clones'...
Afternoon, gang.
Now; some important info I need to impart about the 'clones'.
Recent experience with updating various versions of these has brought to light an issue about which I don't believe I can do anything to fix. It appears that, from v107 onwards, the Chromium Project have now begun to build their browser to expect a far newer build of the Mesa graphics 'stack'.
Any and all attempts to run the 'clones' in anything older than Bionicpup64 - this being the oldest Puppy whose parent is still receiving updates & fixes - will be met with a complete refusal to run. Attempting to launch them from the terminal will inform you about a symbol lookup error:-
Code: Select all
symbol lookup error : undefined symbol : gbm_bo_get_modifierApparently, this was one of a bunch of upgraded instructions added to the Mesa implementation of GBM, and all new Chromium builds are now being being compiled to expect this requirement. For anyone running a "mainstream" distro this is not, in itself, such a 'deal-breaker'; it will probably be addressed in the course of a system update at some point.
For us in Puppyland, given the way Puppies are built, and bearing in mind that most Pups or derivatives thereof don't DO 'updates' - they're pretty much static snapshots in time - it does mean that the only solution will be to move to a newer Puppy IF you wish to continue using an up to date version of ANY Chromium-based browser. Not only will the GBM libraries need to be updated, but in most cases somewhere upwards of 90-odd other dependencies will require updating, and in some cases a complete glibc upgrade will also be required.
This is not something I can really add into a browser package, as it will raise the degree of bloat already present to new & unprecedented levels.....and this is not something I can justify inflicting on other Puppy users. Such a degree of upgrading amounts to a semi-rebuild of whatever Puppy you may be using - we all have our favourites, don't we?
The good news ATM is that Firefox still seems to function more or less OK with some older Pups, though this is of course subject to the long-standing issue of the unpredictable yet somewhat regular browser hangs & freeze-ups that FF has suffered from for ages.
Sorry to be the bearer of bad tidings, but I've been pretty much expecting the next major 'spanner' to drop into the guts of the Chromium Project's product for a while now. Well; it's 'arrived'.....and this time, there isn't anything I can do about it, except to advise everyone to move to relatively new Puppies.
Perhaps somebody else can figure out a more-or-less 'pain-free' workaround to this, but I don't think you're going to find one. There is of course the 'chroot' option, but you not only need a fair dollop of RAM and storage for this to be viable, you'll also need reasonably new hardware to cope with the demands of essentially running TWO Puppies simultaneously on the same machine.
Mike. 
