apenwarr-redo/redo-ifcreate.py

#!/usr/bin/env python2
import sys, os
import vars, state
from logs import err


try:
    me = os.path.join(vars.STARTDIR, 
                      os.path.join(vars.PWD, vars.TARGET))
    f = state.File(name=me)
    for t in sys.argv[1:]:
        if not t:
            err('cannot build the empty target ("").\n')
            sys.exit(204)
        if os.path.exists(t):
            err('redo-ifcreate: error: %r already exists\n' % t)
            sys.exit(1)
        else:
            f.add_dep('c', t)
    state.commit()
except KeyboardInterrupt:
    sys.exit(200)
Replaced all instances of 'python' with 'python2' On systems where 'python' refers to python3, redo failed to launch. All invocations of python have been made explicitly python2 invocations. All tests pass on an Arch Linux system as of this commit. 2018-11-14 10:52:04 -08:00			`#!/usr/bin/env python2`
Add redo-ifcreate to match djb's design. I'm not quite sure why this needs to be a separate program, however, so I'm probably not testing it correctly. 2010-11-13 01:10:43 -08:00			`import sys, os`
Extract .redo dir state management stuff into its own file. In preparation for changing the on-disk format eventually, as well as making the main code more readable. 2010-11-19 03:03:05 -08:00			`import vars, state`
Raw logs contain @@REDO lines instead of formatted data. This makes them more reliable to parse. redo-log can parse each line, format and print it, then recurse if necessary. This got a little ugly because I wanted 'redo --raw-logs' to work, which we want to format the output nicely, but not call redo-log. (As a result, --raw-logs has a different meaning to redo and redo-log, which is kinda dumb. I should fix that.) As an added bonus, redo-log now handles indenting of recursive logs, so if the build was a -> a/b -> a/b/c, and you look at the log for a/b, it can still start at the top level indentation. 2018-11-13 04:05:42 -05:00			`from logs import err`
Add redo-ifcreate to match djb's design. I'm not quite sure why this needs to be a separate program, however, so I'm probably not testing it correctly. 2010-11-13 01:10:43 -08:00

Handle KeyboardInterrupt with less annoying spew to stderr. 2010-11-13 02:09:42 -08:00			`try:`
redo-always/redo-ifcreate/redo-stamp: work inside chdir(). If someone cd's to another directory and then runs redo-always, we weren't adding to the right target. 2010-12-11 23:00:53 -08:00			`me = os.path.join(vars.STARTDIR,`
			`os.path.join(vars.PWD, vars.TARGET))`
			`f = state.File(name=me)`
Handle KeyboardInterrupt with less annoying spew to stderr. 2010-11-13 02:09:42 -08:00			`for t in sys.argv[1:]:`
Print a nicer error message when asked to build an empty string (''). This happens sometimes, for example, if you do whatever \| while read x; do redo-ifchange "$x" done and the input contains blank lines. We could ignore the request for blankness, but it seems like that situation might indicate a more serious bug in your parser, so it's probably better to just abort with a meaningful error. 2018-11-03 03:36:13 -04:00			`if not t:`
			`err('cannot build the empty target ("").\n')`
			`sys.exit(204)`
Handle KeyboardInterrupt with less annoying spew to stderr. 2010-11-13 02:09:42 -08:00			`if os.path.exists(t):`
			`err('redo-ifcreate: error: %r already exists\n' % t)`
			`sys.exit(1)`
			`else:`
redo-always/redo-ifcreate/redo-stamp: work inside chdir(). If someone cd's to another directory and then runs redo-always, we weren't adding to the right target. 2010-12-11 23:00:53 -08:00			`f.add_dep('c', t)`
Add a redo-ifcreate test. Turns out we weren't testing this one at all, which is a shame, because it totally didn't work. 2010-12-11 23:42:31 -08:00			`state.commit()`
Handle KeyboardInterrupt with less annoying spew to stderr. 2010-11-13 02:09:42 -08:00			`except KeyboardInterrupt:`
			`sys.exit(200)`