Thanks, I've missed the LIBCX & NSPR updates.
Now the fun begins trying to sort out which implementation of each dll is the one that works
While my setup may not be perfect (e.g. Lucide has to be started an even number of times, JPEG.DLL in a JAVA142 subdirectory, no latest FF for ArcaOS, no RPM), nowadays getting it right isn't that hard, as long as the system is managed properly. An OS/2 system, i.e. not a Unixified ArcaOS system: if I want Unix, I'll start using Unix.
For example, I've got just 2 copies of Z.DLL by now. The exception is Links, which uses its own copy, and IIRC its WarpIN installer doesn't use the BEGINLIBPATH and LIBPATHSTRICT settings to account for that. So patch the install script, or Rexxify the install script to replace the WarpIN install script. Of course each distributed package with an own Z.DLL has to be checked, but apparently the typical result is that its Z.DLL can be deleted.
I do wish I had recorded which packages are using DLLs like LIBVPX*.DLL, because I'm not sure if I can delete LIBVPX3.DLL and/or LIBVPX4.DLL by now. And I tend to not install hardly ever used software with an excessive number of requirements. GIMP may be an example, despite of packages to install requirements, with Win/OS-2 and Photoshop 2.51 as an abandonware-alternative.