search

xsmile / chromexup

External extension updater for Chromium based browsers
MIT License
13 stars 1 forks source link

Installing extension outside of chrome store #5

Open rEnr3n opened 6 years ago

rEnr3n commented 6 years ago

I want to install this extension but it's not available in the chrome store: https://github.com/dhowe/AdNauseam

https://github.com/dhowe/AdNauseam/wiki/Install-AdNauseam-on-Chrome-Without-Google's-Permission

xsmile commented 6 years ago

chromexup does not have any influence on extensions installed manually or via the Web Store.

rEnr3n commented 6 years ago

So you have no intention in supporting it?

xsmile commented 6 years ago

This is a slightly different use case. Since extensions outside of the Web Store are not published in one single source, you would need to configure different methods to parse the extension version for update checks and to download the extension afterwards. Most of them are probably available in GitHub and it would work, but there is hardly a way you can do it for all possible web sites. You have the same issue with the official Google Chrome browser as you manually need to update all such extensions.

Most probably I won't implement this but I will keep the issue open just in case.

Tank-Missile commented 4 years ago

I would say git is the second best option for delivering extensions, as google has no control in this case. If an extension is removed from the web store for whatever reason, it can still be updated using git. Now, this would require extension developers to standardize releases. A latest tag could be updated as new releases are made. There may be a more feasible option though.

epitron commented 3 years ago

What if the config file could take file paths or urls instead of just extension ids?

eg:

uBlockOrigin = cjpalhdlnbpafiamejdnhcphjbkeiagm
unpackedext  = ~/src/unpackedext
AdNauseam    = https://github.com/dhowe/AdNauseam.git

Since paths/urls always contain a /, disambiguating them is easy.