commit:     8191665432dca1d6cc289185cf7fe32aee0646db
Author:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Sat Aug  3 12:42:09 2019 +0000
Commit:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Thu Aug  8 19:47:42 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=81916654

savedconfig.eclass: Always quote filename in output

Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>

 eclass/savedconfig.eclass | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/eclass/savedconfig.eclass b/eclass/savedconfig.eclass
index f62a6055ffd..1ea464271af 100644
--- a/eclass/savedconfig.eclass
+++ b/eclass/savedconfig.eclass
@@ -128,14 +128,14 @@ restore_config() {
                fi
        done
        if [[ -f ${found} ]]; then
-               elog "Building using saved configfile ${found}"
+               elog "Building using saved configfile \"${found}\""
                if [ $# -gt 0 ]; then
                        cp -pPR "${found}" "$1" || die "Failed to restore 
${found} to $1"
                else
                        die "need to know the restoration filename"
                fi
        elif [[ -d ${found} ]]; then
-               elog "Building using saved config directory ${found}"
+               elog "Building using saved config directory \"${found}\""
                local dest=${PWD}
                pushd "${found}" > /dev/null
                treecopy . "${dest}" || die "Failed to restore ${found} to $1"
@@ -147,7 +147,7 @@ restore_config() {
                        die "Reading config files failed"
                fi
                ewarn "No saved config to restore - please remove 
USE=savedconfig or"
-               ewarn "provide a configuration file in 
${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/${CATEGORY}/${PN}"
+               ewarn "provide a configuration file in 
${PORTAGE_CONFIGROOT%/}/etc/portage/savedconfig/${CATEGORY}/${PN}"
                ewarn "Your config file(s) will not be used this time"
        fi
 }

Reply via email to