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
..
applications	chromium: add ability to control which sandbox is used	2016-08-04 20:37:35 +01:00
build-support	treewide: Add lots of meta.platforms	2016-08-02 21:42:43 +03:00
data	gentium: 1.504 -> 5.000	2016-08-03 09:22:32 +02:00
desktops	Merge branch 'plasma-5.7'	2016-08-04 10:44:43 -05:00
development	haskellPackages.ghc-mod: remove override as 5.6.0.0 is ghc8 compatible	2016-08-04 17:40:17 +01:00
games	treewide: Add lots of meta.platforms	2016-08-02 21:42:43 +03:00
misc	flat-plat: made the theme discoverable	2016-08-04 13:02:22 +02:00
os-specific	Merge pull request #17447 from FRidh/nvidia	2016-08-03 08:36:24 +02:00
servers	varnish: fix localstatedir for varnish* tools (#17508)	2016-08-04 15:25:23 +02:00
shells	Re-enable bunch of packages on Darwin	2016-08-03 00:55:42 +03:00
stdenv	stdenv: ARM bootstrap: Update bootstrap tarballs to hydra-built ones	2016-07-20 18:51:09 +03:00
test
tools	Merge pull request #15967 from ericbmerritt/fix/nixos-container	2016-08-04 16:50:05 +02:00
top-level	ripser: init at 1.0 (#17481)	2016-08-04 10:21:48 +02:00