3
0
Fork 0
forked from mirrors/nixpkgs
nixpkgs/pkgs
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 
2017-06-18 06:19:30 +02:00
..
applications chromium: Allow to put extensions in system path 2017-06-18 06:19:30 +02:00
build-support
common-updater
data
desktops
development Merge pull request from obsidiansystems/ghc-head-doc 2017-06-17 22:08:52 +02:00
games Merge : treewide: setuid/setgid fallout 2017-06-17 13:23:39 +02:00
misc
os-specific linux: 4.9.32 -> 4.9.33 2017-06-17 18:45:29 +02:00
servers Merge pull request from rushmorem/cockroach 2017-06-18 00:46:24 +02:00
shells
stdenv
test
tools Merge : treewide: setuid/setgid fallout 2017-06-17 13:23:39 +02:00
top-level qstopmotion: init -> 2.3.2 2017-06-18 00:47:01 +02:00