On 8/14/14, 5:02 AM, Neil wrote: > Benjamin Smedberg wrote: > >> On 8/13/2014 3:34 AM, Philipp Kewisch wrote: >> >>> Does this also affect binary extensions in any way? I'd imagine that >>> globally installed extensions would break signing if placed >>> incorrectly. >> >> You cannot place anything in the Firefox bundle. Any extensions, >> binary or not, would need to be elsewhere. I don't know that we have >> a supported global install location on Mac. > > Anything? Where does omni.ja go? > omni.ja goes in Contents/Resources[1]. Anything added before signing is okay. After signing, nothing can be added/modified inside of .app/Contents.
We are exploring a workaround where we place/modify files in .app/MozResources after signing[2]. We believe this will work, but we will need to confirm with a working implementation. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1047584 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1047728 _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
