Refactor mac signing scripts for development workflow

chrome/installer/mac/sign_installer_tools.sh

 #!/bin/bash -p
 
 # Copyright 2015 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Using codesign, sign the installer tools. After signing, the signatures are
 # verified.
 
 set -eu
@@ skipping 13 matching lines @@
 
 if [[ ${#} -ne 3 ]]; then
   echo "usage: ${ME} packaging_dir codesign_keychain codesign_id" >& 2
   exit 1
 fi
 
 packaging_dir="${1}"
 codesign_keychain="${2}"
 codesign_id="${3}"
 
-enforcement_flags="restrict,library-validation,kill"
+script_dir="$(dirname "${0}")"
+source "${script_dir}/variables.sh"
 
 executables=(goobspatch xzdec)
 libraries=(liblzma_decompress.dylib)
 declare -a everything
 
 for executable in "${executables[@]}"; do
   sign_path="${packaging_dir}/${executable}"
   everything+=("${sign_path}")
 
   codesign --sign "${codesign_id}" --keychain "${codesign_keychain}" \
-      "${sign_path}" --options "${enforcement_flags}"
+      "${sign_path}" --options "${enforcement_flags_tools}"

[Mark Mentovai, 2017/04/25 02:02:24]

No custom requirement action here? Now that the requirements are centralized, is
it more sensible?

[Mark Mentovai, 2017/04/25 02:02:25]

enforcement_flags_installer_tools? “tools” is a little ambiguous otherwise.

[Greg K, 2017/04/25 18:45:21]

Done.

 done
 
 for library in "${libraries[@]}"; do
   sign_path="${packaging_dir}/${library}"
   everything+=("${sign_path}")
 
   codesign --sign "${codesign_id}" --keychain "${codesign_keychain}" \
       "${sign_path}"
 done
 
 for sign_path in "${everything[@]}"; do
   codesign --verify --deep -vvvvvv "${sign_path}"
 done