nixpkgs-suyu/pkgs/applications/networking/browsers
aszlig 7e10ecb763
chromium: Allow to put extensions in system path
This should allow us to easily add system-wide Chromium extensions via a
NixOS configuration similar to this:

{ pkgs, ... }: {
  environment.pathsToLink = [ "/share/chromium/extensions" ];
  environment.systemPackages = [ pkgs.my-shiny-extension ];
}

For more details about what Chromium expects within that directory, see:

https://developer.chrome.com/extensions/external_extensions

I've introduced this because of a personal desire to gain more control
about which extensions are installed and what they are able to do. All
of the extensions I use are free software, but despite that it's useful
to either easily patch them and also prevent unwanted automatic updates.

Tested this using the NixOS "chromium.stable" test on x86_64-linux.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @offlinehacker because of #21050
2017-06-18 06:19:30 +02:00
..
arora
chromium chromium: Allow to put extensions in system path 2017-06-18 06:19:30 +02:00
conkeror
dillo
dwb
elinks
firefox firefox-esr: 52.1.2esr -> 52.2.0esr 2017-06-14 22:46:23 +09:00
firefox-bin Merge #26601: thunderbird*: 52.1.1 -> 52.2.0 (security) 2017-06-15 20:29:01 +02:00
google-chrome chrome: fix fallout from #26512 2017-06-16 14:40:28 -04:00
jumanji
links2 treewide: purge maintainers.urkud 2017-03-27 19:52:29 +02:00
lynx lynx: Fix SSL, widec support (#26134) 2017-05-29 15:14:02 +08:00
midori
mozilla-plugins flash: 26.0.0.126 -> 26.0.0.131 2017-06-16 14:42:45 -04:00
opera Opera: 44.0.2510.857 -> 45.0.2552.812 2017-05-19 19:48:28 -04:00
palemoon palemoon: 27.1.1 -> 27.2.1 2017-03-28 04:39:52 -04:00
qutebrowser qutebrowser: cleanup wrappers 2017-04-13 00:07:01 +03:00
surf surf: 0.7 -> 2.0 2017-04-02 20:11:44 +02:00
tor-browser-bundle-bin tor-browser-bundle-bin: 7.0 -> 7.0.1 2017-06-14 23:33:45 +02:00
uzbl
vimb
vimprobable2
vivaldi vivaldi: fix space in sha256 2017-06-15 17:48:49 +00:00
w3m w3m: fix package name 2017-01-21 15:02:02 +02:00