apenwarr-redo/vars.py

import os

TARGET = os.environ.get('REDO_TARGET', '')
DEPTH = os.environ.get('REDO_DEPTH', '')
DEBUG = os.environ.get('REDO_DEBUG', '') and 1 or 0
VERBOSE = os.environ.get('REDO_VERBOSE', '') and 1 or 0
SHUFFLE = os.environ.get('REDO_SHUFFLE', '') and 1 or 0
STARTDIR = os.environ.get('REDO_STARTDIR', '')
BASE = os.environ.get('REDO_BASE', '')
if BASE:
    BASE = os.path.abspath(BASE)
    while BASE and BASE.endswith('/'):
        BASE = BASE[:-1]
Use a single .redo dir for the entire build. 2010-11-12 22:47:03 -08:00			`import os`

Move log stuff into a separate log.py. 2010-11-13 00:11:34 -08:00			`TARGET = os.environ.get('REDO_TARGET', '')`
			`DEPTH = os.environ.get('REDO_DEPTH', '')`
			`DEBUG = os.environ.get('REDO_DEBUG', '') and 1 or 0`
			`VERBOSE = os.environ.get('REDO_VERBOSE', '') and 1 or 0`
Add a --shuffle option to let you enable dependency randomization. Previously, for testing, we were always randomizing the build order of dependencies. That's annoying since it'll make build logs differ randomly from one run to the next, which could make comparisons harder. However, the feature is still useful for uncovering hidden dependencies between objects. 2010-11-16 00:14:57 -08:00			`SHUFFLE = os.environ.get('REDO_SHUFFLE', '') and 1 or 0`
Fix log() output so you can cut-and-paste it verbatim into a command line. It used to say: redo: t/all redo: hello and now it says: redo t/all redo t/hello ie. there's no colon, and the path is intact. That means if the build fails, you can cut-and-paste 'redo t/hello', add a -v, and try to debug what went wrong. 2010-11-13 01:55:07 -08:00			`STARTDIR = os.environ.get('REDO_STARTDIR', '')`
Don't throw a weird exception if REDO_BASE isn't set. 2010-11-13 01:08:28 -08:00			`BASE = os.environ.get('REDO_BASE', '')`
			`if BASE:`
			`BASE = os.path.abspath(BASE)`
			`while BASE and BASE.endswith('/'):`
			`BASE = BASE[:-1]`