On Sun, 07 Apr 2019 13:46:33 +0200 Markus Koschany wrote: > Thoughts?
There is a better option for this: Keep the one package but install a different manifest.json into the Firefox and Chrome extension directories. This should work since Firefox and Chrome look for their extensions in different directories. The only issue with this workaround is that it involves instead of just symlinking the directory, symlinking every file except manifest.json. The per-browser manifest.json should probably be created at build time. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
