fixes #66

Makefile

@@ -1,4 +1,4 @@
-VERSION = 2.208
+VERSION = 2.209
 PN = clean-chroot-manager
 
 PREFIX ?= /usr

common/clean-chroot-manager64.in

@@ -1,7 +1,10 @@
 #!/bin/bash
+
+#
 # clean-chroot-manager by graysky
 #
-# See the man page for more.
+
+# shellcheck disable=1090
 
 VERS='@VERSION@'
 PKG='clean-chroot-manager'

doc/clean-chroot-manager.1

@@ -1,14 +1,14 @@
 .\" Text automatically generated by txt2man
-.TH clean-chroot-manager 1 "09 May 2020" "" ""
+.TH clean-chroot-manager 1 "25 May 2020" "" ""
 .SH NAME
 \fBClean-chroot-manager \fP- Wrapper script to manage buildroots when building packages under Arch Linux.
 \fB
 .SH DESCRIPTION
-Ccm provides a "one-click" solution for building packages in a clean buildroot. Two key points that differentiate using ccm from the using the arch-build-scripts alone:
+mcm provides a "one-click" solution for building packages in a clean buildroot. Two key points that differentiate using ccm from the using the arch-build-scripts alone:
 .IP \(bu 3
-Ccm automatically manages a local "staging" repo within the buildroot itself, so anything you build (dependencies from the AUR or more current versions of repo packages, etc.) are transparently pulled from that local repo.
+mcm automatically manages a local "staging" repo within the buildroot itself, so anything you build (dependencies from the AUR or more current versions of repo packages, etc.) are transparently pulled from that local repo.
 .IP \(bu 3
-Ccm can optionally build with distcc.
+mcm can optionally build with distcc.
 .PP
 To expand on point 1: let's say that we want to build a package called "bar" from the AUR but bar has a build dependency of another AUR package called "foo." Rather than first building foo, then installing foo, then building bar, and finally removing foo, the local repo will save a copy of the foo package which is indexed automatically therein. Pacman within the buildroot is aware of the foo package thanks to the local repo. When we try to build bar, pacman silently grabs the foo package from the local repo as it would any other dependency.
 .PP
@@ -132,6 +132,8 @@ Deletes everything under the top level of the buildroot effectively removing it
 .SH BUGS
 .IP \(bu 3
 Not really a bug, but know that if you modify your config file after you created a buildroot, the changes will not be effective until you nuke and rebuild the buildroot.
+.IP \(bu 3
+ccm may fail to move packages to a custom PKGDEST if you define it to be outside of the chroot itself. See #30 on github.
 .PP
 Discover a bug? Please open an issue on the project page linked below.
 .SH ONLINE