obadz 33557acb36 chromium: add ability to control which sandbox is used ... First step towards addressing #17460 In order to be able to run the SUID sandbox, which is good for security and required to run Chromium with any kind of reasonable sandboxing when using grsecurity kernels, we want to be able to control where the sandbox comes from in the Chromium wrapper. This commit patches the appropriate bit of source and adds the same old sandbox to the wrapper (so it should be a no-op)		2016-08-04 20:37:35 +01:00
..
patches	chromium: Update dev channel to v52.0.2743.10	2016-05-28 19:15:39 +02:00
browser.nix	Do some large, concurrency-capable builds on dedicated machines	2016-05-04 18:16:27 +02:00
common.nix	chromium: add ability to control which sandbox is used	2016-08-04 20:37:35 +01:00
default.nix	chromium: add ability to control which sandbox is used	2016-08-04 20:37:35 +01:00
plugins.nix	makeSearchPathOutputs: refactor to makeSearchPathOutput	2016-04-25 13:24:39 +03:00
update.nix	chromium/updater: Don't import <nixpkgs> again	2016-05-04 22:35:24 +02:00
update.sh	chromium/source: Move update.nix to parent dir	2016-03-20 16:53:08 +01:00
upstream-info.nix	Update google-chrome versions	2016-08-04 00:22:58 -04:00