summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Shumaker <lukeshu@parabola.nu>2016-05-09 18:37:02 -0400
committerLuke Shumaker <lukeshu@parabola.nu>2018-01-03 14:58:21 -0500
commitaedd3438ffdc764a0729b62855b5cb3997f11627 (patch)
tree3d9b5c9755e16c35d083a3c31dd284381512c928
parent61b1718f50083632e42decb35ebed7c2f188d558 (diff)
downloaddevtools32-aedd3438ffdc764a0729b62855b5cb3997f11627.tar.xz
arch-nspawn: Message style: two spaces after a period
This affects both the usage() text, and the error message if the `/.arch-chroot` version doesn't match. The latter is the one that I really care about, and motivates this change. On Parabola, the `arch-nspawn` program isn't in PATH, it's somewhere under `/usr/lib/`, and gets called as a helper to user-facing programs; and the error message is displayed directly to the user. These programs consistently put two spaces after a period when printing a message to the terminal.
-rw-r--r--arch-nspawn.in4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch-nspawn.in b/arch-nspawn.in
index 7a7a274..7723241 100644
--- a/arch-nspawn.in
+++ b/arch-nspawn.in
@@ -19,7 +19,7 @@ files=()
usage() {
echo "Usage: ${0##*/} [options] working-dir [systemd-nspawn arguments]"
- echo "A wrapper around systemd-nspawn. Provides support for pacman."
+ echo "A wrapper around systemd-nspawn. Provides support for pacman."
echo
echo ' options:'
echo ' -C <file> Location of a pacman config file'
@@ -101,7 +101,7 @@ umask 0022
if [[ ! -f "$working_dir/.arch-chroot" ]]; then
die "'%s' does not appear to be an Arch chroot." "$working_dir"
elif [[ $(cat "$working_dir/.arch-chroot") != "$CHROOT_VERSION" ]]; then
- die "chroot '%s' is not at version %s. Please rebuild." "$working_dir" "$CHROOT_VERSION"
+ die "chroot '%s' is not at version %s. Please rebuild." "$working_dir" "$CHROOT_VERSION"
fi
build_mount_args