Linux: fix for developing on a machine with google-chrome packages installed.

The latest google-chrome packages contain a sandbox binary, which the
development builds of chromium will pick up on automatically. However,
for safety reasons, the sandbox binary will only exec a fixed chrome
binary location. Since development builds will be somewhere else in
the filesystem, this means that they will fail to start their zygote
processes and generally be very sad.

However, we /do/ want people developing with the sandbox, but we don't
want the general sandbox binary to be able to exec anything. We could
have chromium try and find its sandbox binary relative to the build
directory, but some people build on NFS and, since the sandbox binary
needs to be SUID, this won't work for them.

Instead, we add a new target: chrome_devel_sandbox which developers
can use. This builds a sandbox binary that will exec anything which is
owned by the running user. This alternative sandbox binary can be
selected by exporting CHROME_DEVEL_SANDBOX.


git-svn-id: http://src.chromium.org/svn/trunk/src/build@20709 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

common.gypi

@@ -83,6 +83,14 @@
     'chromeos%': 0,
 
     'chrome_personalization%': 0,
+
+    # Set the restrictions on the SUID sandbox binary.
+    #  Path: only exec the hard coded chrome binary path
+    #  User: only exec binaries owned by the running user.
+    #
+    # Developers should read
+    #  http://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment
+    'linux_suid_sandbox_restrictions': 'Path',
   },
   'target_defaults': {
     'conditions': [