From 4722ea598edd6b630227404c48c1c09ac527e9b8 Mon Sep 17 00:00:00 2001 From: Mohammad Akhlaghi Date: Sun, 14 Apr 2019 17:48:40 +0100 Subject: Replaced all occurances of pipeline in text All occurances of "pipeline" have been chanaged to "project" or "template" withint the text (comments, READMEs, and comments) of the template. The main template branch is now also named `template'. This was all because `pipeline' is too generic and couldn't be distinguished from the base, and customized project. --- configure | 117 +++++++++++++++++++++++++++++++------------------------------- 1 file changed, 59 insertions(+), 58 deletions(-) (limited to 'configure') diff --git a/configure b/configure index 19a5acd..8091b4e 100755 --- a/configure +++ b/configure @@ -1,6 +1,6 @@ #! /bin/bash # -# Necessary preparations/configurations for the reproduction pipeline. +# Necessary preparations/configurations for the reproducible project. # # Copyright (C) 2018-2019 Mohammad Akhlaghi # @@ -56,15 +56,15 @@ information printed before them). Alternatively, if you have already configured this script for your system, you can use the '--existing-conf' to use its values directly. -RECOMMENDATION: If this is the first time you are running this pipeline, +RECOMMENDATION: If this is the first time you are running this template, please don't use the options and let the script explain each parameter in full detail by simply running './configure'. -The only mandatory value for this script is the local build directory. This -is where all the pipeline's outputs will be stored. Optionally, you can -also provide directories that host input data, or software source codes. If -the necessary files don't exist there, the template will automatically -download them. +The only mandatory value is the local build directory. This is where all +the (temporary) built files will be stored. Optionally, you can also +provide directories that host input data, or software source codes. If the +necessary files don't exist there, the template will automatically download +them. With the options below you can modify the default behavior. Just note that you should not put an '=' sign between an option name and its value. @@ -216,14 +216,13 @@ function create_file_with_notice() { if echo "# IMPORTANT: file can be RE-WRITTEN after './configure'" > "$1" then echo "#" >> "$1" - echo "# This file was created during the reproduction" >> "$1" - echo "# pipeline's configuration ('./configure'). Therefore," >> "$1" - echo "# it is not under version control and any manual " >> "$1" - echo "# changes to it will be over-written if the pipeline " >> "$1" - echo "# is re-configured." >> "$1" + echo "# This file was created during configuration" >> "$1" + echo "# ('./configure'). Therefore, it is not under version" >> "$1" + echo "# control and any manual changes to it will be" >> "$1" + echo "# over-written if the project re-configured." >> "$1" echo "#" >> "$1" else - echo; echo "Can't write to "$1""; echo; + echo; echo "Can't write to $1"; echo; exit 1 fi } @@ -256,15 +255,13 @@ function absolute_dir() { # on and is prepared on what will happen next. cat <