Cross-repo recipe package system.

scripts/slave/recipes.py

+#!/usr/bin/env python
+
+"""Bootstrap script to clone and forward to the recipe engine tool."""
+
+import os
+import subprocess
+import sys
+
+SCRIPT_DIR = os.path.dirname(os.path.realpath(__file__))
+REPO_ROOT = os.path.dirname(os.path.dirname(SCRIPT_DIR))
+ENGINE_REPO = '/b/build'
+ENGINE_BRANCH = 'recipe-packages'
+ENGINE_DIR = os.path.join(SCRIPT_DIR, '.recipe_engine')
+ENGINE_SUBDIR = os.path.join(ENGINE_DIR, 'third_party', 'recipe_engine')
+
+if not os.path.exists(ENGINE_DIR):

[iannucci, 2015/08/06 23:57:12]

let's use `git rev-parse --something` to find the root directory and calculate
the abspath for .recipe_engine.

want to start making a README for the new repo:
  * copy this script into your repo (at "path"?)
  * add .recipe_engine to your .gitignore
  * what are all the assumptions about where stuff goes (e.g. for the roller)
  * ...?

let's make all the bootstrap stuff live in a subdirectory, maybe, and then clone
a subtree of that, just to keep the amount of stale code at a minimum. Then we
can have a README in that bootstrap directory describing how changes to that
directory need to propagate differently than the rest of the repo.

Maybe fetch it to HEAD 1/day in this script?

+  subprocess.check_call(['git', 'clone', ENGINE_REPO, ENGINE_DIR])
+
+  # TODO(luqui): this stuff is just for pre-move testing
+  cwd = os.getcwd()
+  os.chdir(ENGINE_DIR)
+  subprocess.check_call(['git', 'reset', '--hard', 'origin/%s' % ENGINE_BRANCH])
+  os.chdir(cwd)
+
+args = [sys.argv[0]] + ['--package', REPO_ROOT] + sys.argv[1:]
+os.execvp(os.path.join(ENGINE_SUBDIR, 'recipes.py'), args)