search

pdf / kdeconnect-chrome-extension

A browser extension to send pages and content from your browser to connected KDE Connect devices.
https://chrome.google.com/webstore/detail/kde-connect/ofmplbbfigookafjahpeepbggpofdhbo
MIT License
233 stars 29 forks source link

unsupervised installation to custom prefix #22

Open flying-sheep opened 6 years ago

flying-sheep commented 6 years ago

It doesn’t seem like the install script is packaging friendly. in order to create a package, I need to:

  1. invoke the install script purely via CLI parameters and/or env variables (i.e. ./kdeconnect-chrome-extension -install ... </dev/null has be possible)
  2. do a install like your root mode, but to a custom prefix directory (install everything to /path/to/my/packagedir instead of / and without being root)
pdf commented 6 years ago

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.

flying-sheep commented 6 years ago

I prefer the workflow vs the official one

I think this is what I wanted to figure out, but I’d never install things to system directories without packaging it properly, hence this issue.