forks/apenwarr-redo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
apenwarr-redo/vars.py

23 lines
843 B
Python
Raw Normal View History

Use a single .redo dir for the entire build.
2010-11-12 22:47:03 -08:00
import os
Move atoi() into atoi.py and add a new debug2() debug level. atoi() was getting redundant, and unfortunately we can't easily load helpers.py in some places where we'd want to, because it depends on vars.py. So move it to its own module.
2010-11-16 04:13:17 -08:00
import atoi
Use a single .redo dir for the entire build.
2010-11-12 22:47:03 -08:00
redo-if{change,create}: print a useful message if REDO isn't set. Again, I forgot to make vars.py not crash if the variables aren't set, so we can print a useful error message. But this time I have the right solution: vars.py will do the checking for itself, and abort with a nice message.
2010-11-22 02:45:00 -08:00
if not os.environ.get('REDO'):
import sys
sys.stderr.write('%s: error: must be run from inside a .do\n'
% sys.argv[0])
sys.exit(100)
Remove the need for relpath (and thus abspath) in builder.py.
2010-11-21 03:34:32 -08:00
PWD = os.environ.get('REDO_PWD', '')
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', '')
Move atoi() into atoi.py and add a new debug2() debug level. atoi() was getting redundant, and unfortunately we can't easily load helpers.py in some places where we'd want to, because it depends on vars.py. So move it to its own module.
2010-11-16 04:13:17 -08:00
DEBUG = atoi.atoi(os.environ.get('REDO_DEBUG', ''))
Add a --debug-locks option. Get rid of the "locked..." and "...unlocked!" messages by default, since they're not usually interesting. But add a new option to bring them back in case we end up with trouble debugging the locking stuff. (I don't really 100% trust it yet, although I haven't had a problem for a while now.)
2010-11-21 06:23:41 -08:00
DEBUG_LOCKS = os.environ.get('REDO_DEBUG_LOCKS', '') and 1 or 0
Add a new --debug-pids option. This makes the helpers.* log functions prepend getpid() to each line, so you can see which pid did what.
2010-11-22 01:50:46 -08:00
DEBUG_PIDS = os.environ.get('REDO_DEBUG_PIDS', '') and 1 or 0
Move log stuff into a separate log.py.
2010-11-13 00:11:34 -08:00
VERBOSE = os.environ.get('REDO_VERBOSE', '') and 1 or 0
Add a -x option that just passes -x to the subshell. This is often more useful than -v, since it prints the actual commands being executed, not just the lines being input from the script.
2010-11-21 06:35:52 -08:00
XTRACE = os.environ.get('REDO_XTRACE', '') and 1 or 0
Add a new -k (--keep-going) option, like make has. Previously, the default was to *always* keep going, which is actually not usually what you want. Now we actually exit correctly after an error. Of course you still might have multiple errors before existing if you were building in parallel.
2010-11-21 07:10:48 -08:00
KEEP_GOING = os.environ.get('REDO_KEEP_GOING', '') 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
vars.py: it's safe to assume REDO_BASE and REDO_STARTDIR are set correctly. This lets us remove an extra call to os.abspath().
2010-11-21 03:09:21 -08:00
STARTDIR = os.environ['REDO_STARTDIR']
BASE = os.environ['REDO_BASE']
while BASE and BASE.endswith('/'):
BASE = BASE[:-1]
Reference in a new issue Copy permalink