Package Details: chromexup 0.5.1-3

Git Clone URL: (read-only, click to copy)
Package Base: chromexup
Description: External extension updater for Chromium based browsers
Upstream URL:
Keywords: browser chromium extension inox iridium ungoogled updater
Licenses: MIT
Submitter: xsmile
Maintainer: xsmile
Last Packager: xsmile
Votes: 6
Popularity: 0.097760
First Submitted: 2018-03-21 19:34
Last Updated: 2020-12-02 08:42

Latest Comments

cryzed commented on 2018-08-04 22:47

Oh, I actually just made something super similiar:

For naught apparently, this looks great. Thanks!

xsmile commented on 2018-03-22 15:06

The --extdir argument is gone. Instead the browser user data directory can be set with the branding config key, see the updated template file for examples.

@rEnr3n Fixed, thank you.

@sekret I prefer having a configuration file for each browser. To add another one, you can create an additional set of systemd scripts in your user directory pointing to another configuration file with the --cfgfile argument.

Your idea can even be expanded by having a single directory for all extensions to avoid duplicates and placing symlinks to activate different extensions for each browser. I would like to keep it simpler though.

sekret commented on 2018-03-22 07:38

I like the idea of including it in the configuration file! You could provide a list of known directories for different chromium variants. Something like

Configuration file for chromexup.


Parallel download threads.

parallel_downloads = 4

Remove extensions not defined in the extension section.

remove_orphans = True

[inox] path = ~/.config/inox HTTPSEverywhere = gcbommkclmclpchllfjekcdonpmejbdp uMatrix = ogfcmafjalglgifnmanfmnieipoejdcf

[iridium] path = ~/.config/iridium uBlockOrigin = cjpalhdlnbpafiamejdnhcphjbkeiagm

rEnr3n commented on 2018-03-22 01:23

There's a typo in chromexup-daily.timer

Description should say daily instead of weekly.

xsmile commented on 2018-03-21 23:46

config.ini.example will be installed correctly now.

The most convenient solution for different Chromium variants is probably not to assume a default user data directory at all and to let the user specify it in the configuration file. This way the systemd service doesn't need to be touched. If only a single browser is installed, it could theoretically be found using by using a pre-set list of known directories. On the other hand I can't possibly know how the user wants to handle extensions if multiple variants are found, e.g. Chromium and Inox.

In the meantime you can edit the service file and append '--extdir "%h/.config/inox/External Extensions"' to the executable name, or simply use a symlink :P I will push another version soon.

Thanks for the feedback and don't hesitate if you have any other suggestions.

sekret commented on 2018-03-21 20:41

According to your install script, there should be a file


but it's not included in the package. Please add a line to the package function which includes this file in the package.

So when I first started the application, I got this:

$ chromexup [INFO] creating directory /home/sekret/.config/chromium/External Extensions Traceback (most recent call last): File "/usr/bin/chromexup", line 11, in <module> load_entry_point('chromexup==0.3.0', 'console_scripts', 'chromexup')() File "/usr/lib/python3.6/site-packages/chromexup/", line 270, in main check(args.cfgfile, args.extdir) File "/usr/lib/python3.6/site-packages/chromexup/", line 142, in check os.mkdir(ext_dir, 0o755) FileNotFoundError: [Errno 2] No such file or directory: '/home/sekret/.config/chromium/External Extensions'</module>

Looks like your application requires an already existing ~/.config/chromium folder. But what if I e.g. use inox? I know then I have to prepare stuff via symlinks. All I'm saying is, there's room for improvement :-)

Nice app btw, thanks for sharing it :-)