You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for the delay in responding - I've been travelling the last couple of months.
I can take a look at implementing the menus as CLI params or env vars, though that's slightly complicated by stuff like multi-value options for multiple browser installs. If you wanted to package it as is, all the install flag does is generate native host json configuration appropriate for the selected browsers (only firefox uses a different format - the others are all the same) and copies the kdeconnect-chrome-extension binary, so if you run the installer once, grab the json configs, and modify them to point to the custom install location for the binary, then deploy the json configs as part of the package, that should work.
Side note, are you aware of the official browser extension? I still use this one, because I prefer the workflow vs the official one, but it might suit your needs and is probably packaged already.
It doesn’t seem like the install script is packaging friendly. in order to create a package, I need to:
./kdeconnect-chrome-extension -install ... </dev/null
has be possible)/path/to/my/packagedir
instead of/
and without being root)The text was updated successfully, but these errors were encountered: