===========================================================
                                      .___ __  __   
          _________________  __ __  __| _/|__|/  |_ 
         / ___\_` __ \__  \ |  |  \/ __ | | \\_  __\
        / /_/  >  | \// __ \|  |  / /_/ | |  ||  |  
        \___  /|__|  (____  /____/\____ | |__||__|  
       /_____/            \/           \/           
              grep rough audit - static analysis tool
                  v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
cl-launch-4.1.4/00INSTALL-36-You can decide separately where the binary will be using ``INSTALL_BIN``
cl-launch-4.1.4/00INSTALL:37:(to override the default of ``$PREFIX/bin``)
cl-launch-4.1.4/00INSTALL-38-and where the Lisp source code will go using ``INSTALL_SOURCE``
cl-launch-4.1.4/00INSTALL:39:(to override the default of ``$PREFIX/share/common-lisp/source/cl-launch``)
cl-launch-4.1.4/00INSTALL-40-with a symlink to the asd file going in ``INSTALL_SYSTEMS``
cl-launch-4.1.4/00INSTALL:41:(to override the default of ``$PREFIX/share/common-lisp/systems``).
cl-launch-4.1.4/00INSTALL-42-
##############################################
cl-launch-4.1.4/00INSTALL-51-and if not for a judicious symlink
cl-launch-4.1.4/00INSTALL:52:from ``$HOME/bin/cl-launch`` to my checkout,
cl-launch-4.1.4/00INSTALL-53-it would also do::
##############################################
cl-launch-4.1.4/Makefile-33-	@mkdir -p ${INSTALL_SYSTEMS}/
cl-launch-4.1.4/Makefile:34:	@if [ `dirname ${INSTALL_SYSTEMS}`/source/cl-launch = ${INSTALL_SOURCE} ] ; then \
cl-launch-4.1.4/Makefile-35-		ln -sf ../source/cl-launch/cl-launch.asd ${INSTALL_SYSTEMS}/ ; \
##############################################
cl-launch-4.1.4/cl-launch.sh-498-files \`/etc/cl-launchrc\` and \`~/.cl-launchrc\`.
cl-launch-4.1.4/cl-launch.sh:499:These files are notably useful to define override the value of \`\$LISP\`
cl-launch-4.1.4/cl-launch.sh:500:depending on \`\$SOFTWARE_SYSTEM\`. A shell function \`system_preferred_lisps\`
cl-launch-4.1.4/cl-launch.sh-501-is provided so that your \`cl-launchrc\` might contain lines as follows:
##############################################
cl-launch-4.1.4/cl-launch.sh-602-and/or to .../lispworks/lib/7-0-0-0/config/lwlicense
cl-launch-4.1.4/cl-launch.sh:603:(or use a trampoline shell script to \`exec /path/to/lispworks "\$@"\`),
cl-launch-4.1.4/cl-launch.sh-604-create a build script with:
##############################################
cl-launch-4.1.4/cl-launch.sh-611-4.1.2.1, \`lispworks-console\` is assumed instead, to avoid conflicts. You can
cl-launch-4.1.4/cl-launch.sh:612:control the name you use with the shell variable \`\$LISPWORKS\`, or you
cl-launch-4.1.4/cl-launch.sh-613-can just leave \`lispworks-console\` in your path, and use a symlink, copy,
##############################################
cl-launch-4.1.4/cl-launch.sh-672-the capitalization of the given nickname.
cl-launch-4.1.4/cl-launch.sh:673:Hence, variable \`\$SBCL\` controls where to look for the \`sbcl\` implementation,
cl-launch-4.1.4/cl-launch.sh:674:and variable \`\$CMUCL\` controls where to look for the \`cmucl\` implementation.
cl-launch-4.1.4/cl-launch.sh:675:If a binary is found with a matching pathname (using the standard unix \`\$PATH\`
cl-launch-4.1.4/cl-launch.sh-676-as required), then said implementation will be used, using proper command line
##############################################
cl-launch-4.1.4/cl-launch.sh-678-but with \`_OPTIONS\` appended to its name.
cl-launch-4.1.4/cl-launch.sh:679:Hence, \`\$CMUCL_OPTIONS\` for \`cmucl\`, \`\$CLISP_OPTIONS\` for \`clisp\`, etc.
cl-launch-4.1.4/cl-launch.sh-680-Sensible defaults are provided for each implementation, so as to execute the
##############################################
cl-launch-4.1.4/cl-launch.sh-704-
cl-launch-4.1.4/cl-launch.sh:705:Note that you can use option \`--wrap "\$(cat your_script)"\`
cl-launch-4.1.4/cl-launch.sh-706-to embed into your program a full fledged script from a file.
##############################################
cl-launch-4.1.4/cl-launch.sh-781-
cl-launch-4.1.4/cl-launch.sh:782:(Actually \`"\$@"\` instead of \`\${1+"\$@"}\` should work just fine,
cl-launch-4.1.4/cl-launch.sh-783-unless you have an antique shell.)
##############################################
cl-launch-4.1.4/cl-launch.sh-2131-    return 0
cl-launch-4.1.4/cl-launch.sh:2132:  elif LISP_BIN="`which "$1" 2> /dev/null`" ; then
cl-launch-4.1.4/cl-launch.sh-2133-    return 0