Unnecessary copy operations in profile folder about pwasforfirefox HOT 3 CLOSED

I added a check to only copy files to the profile if the global chrome/pwa/chrome.jsm is newer than the profile file. Because that file contains version, it should be automatically copied on every release. Always copying files can still be enabled in the extension settings. Note that on macOS it still copies files every time, because this is needed to properly set PWA name.

from pwasforfirefox.

It only overwrites/copies chrome/pwa and startupCache in the profile, and _autoconfig.cfg and defaults/pref/autoconfig.js in the Firefox installation (and some additional files on macOS, but this is actually needed on every launch so OS integration works correctly). I did this to make sure UserChrome stuff is always up-to-date, as updating them when package updates would be harder because user may have multiple OS and Firefox profiles.

Maybe the program could do this only when files actually differ from the latest installed version (C:\Program Files\FirefoxPWA\userchrome on Windows) but I'm not sure what the best way of checking if files need update would be. Perhaps it could check the hash/content of chrome/pwa/chrome.jsm as it contains package version which should be changed with every new release.

from pwasforfirefox.

What about a script that only runs on package updates/installations to reduce overwrites. Should that not be possible? Your idea also sounds good. Maybe you could do that with an extra version file. But to be honest, I do not know to much about this topic. This behaviour just stood out to me while I was messing with the files in chrome/pwa and thought I should tell you.

from pwasforfirefox.