Skip to content

Commit 7e10ecb

Browse files
committedJun 18, 2017
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
1 parent 63b8d65 commit 7e10ecb

File tree

1 file changed

+3
-0
lines changed
  • pkgs/applications/networking/browsers/chromium

1 file changed

+3
-0
lines changed
 

Diff for: ‎pkgs/applications/networking/browsers/chromium/common.nix

+3
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,9 @@ let
132132
:l; n; bl
133133
}' gpu/config/gpu_control_list.cc
134134
135+
# Allow to put extensions into the system-path.
136+
sed -i -e 's,/usr,/run/current-system/sw,' chrome/common/chrome_paths.cc
137+
135138
patchShebangs .
136139
# use our own nodejs
137140
mkdir -p third_party/node/linux/node-linux-x64/bin

0 commit comments

Comments
 (0)
Please sign in to comment.