The previous method was only writing the .txt file; when debugging
dependency issues you'll often want to see the intermediate. I don't
see a reason to not always write it.
Signed-off-by: Zack Cerza <zack@redhat.com>
#!/bin/bash
-pip-compile $@ requirements.in -qo- | sed -e '/^-e / d' -e 's/-r requirements.in/teuthology/g' > requirements.txt
+pip-compile $@ requirements.in
+sed -i'' -e '/^-e / d' -e 's/-r requirements.in/teuthology/g' requirements.txt
\ No newline at end of file