Closed mvo5 closed 6 years ago
I think this was mostly because we cargo culted this from UC16 which used synced dirs so that we could bring in new bits via the core snap into the writable paths. But we learned the hard way that "synced" is more harmful than helpful so we decided to not use it on core18.
Also add test that ensures "synced" dirs are no longer used and run hooks after static content.
The "synced" filemode for the writable-paths had resulted in subtle bugs in the past. One issue is that it is not possible to delete a file in "synced" mode, because writable-paths will always re-create the file from the core18 image. There are more subtle issues so we should not rely on this.