@@ -44,8 +44,11 @@ Each sub-directory should contain one or more .in files with corresponding .txt
file. Base names must match (i.e. if you have production.in, the requirements
file must be called production.txt).
Utility iterates over each .in/.txt pair, calculates new requirements based on
the .in file, and diffs this against existing .txt file.
Utility iterates over each .in/.txt pair, calculates new requirements
based on the .in file, and diffs this against existing .txt file. If a
.in file does not have a corresponding .txt file, it is ignored
(making it possible to use the '-r base.in' syntax for including base
requirements etc).
Utility creates copy of existing requirements file, stripping it from all
comments, then calculates new requirements file (storing result in temporary
@@ -245,7 +248,7 @@ for environment in "$config_dir"/*; do
# Figure out if .txt file exists.
req_txt="${req_in%.in}.txt"
if [[ ! -f $req_txt ]]; then
warning "Missing .txt file for: $req_in"
[[ $quiet == 0 ]] && info "Skipping input file with missing .txt file: $req_in"
continue
fi