kiss/contrib/kiss-repodepends

#!/bin/sh
# Display a package's original dependencies.

# Ignore shellcheck as we want the warning's behavior.
# shellcheck disable=2015
[ "$1" ] && kiss s "${1:-null}" >/dev/null || {
    printf 'usage: kiss-repodepends [pkg]\n'
    exit 1
}

cat "$(kiss s "$1")/depends" 2>/dev/null
kiss: Merge kiss-utils and kiss 2019-10-30 04:51:48 -06:00			`#!/bin/sh`
kiss: Integrate with user scripts. kiss' help output will now include all executables found in $PATH which begin with kiss-*. A comment string is optionally usable via setting the second line of the script to a string. Example: ... This also means that 'kiss <script name>' is also possible now. If I have a script in my $PATH called kiss-depends, I can now use it via kiss with 'kiss depends'. 2020-04-18 02:39:37 -06:00			`# Display a package's original dependencies.`
kiss: Merge kiss-utils and kiss 2019-10-30 04:51:48 -06:00
kiss: Unify usage outputs for all contrib scripts. Seeing as how these utilities are now better integrated, more effort should go into the overall interface between what should be the "benchmark" or example kiss scripts. 2020-04-18 03:11:56 -06:00			`# Ignore shellcheck as we want the warning's behavior.`
			`# shellcheck disable=2015`
			`[ "$1" ] && kiss s "${1:-null}" >/dev/null \|\| {`
			`printf 'usage: kiss-repodepends [pkg]\n'`
			`exit 1`
			`}`

kiss: Integrate with user scripts. kiss' help output will now include all executables found in $PATH which begin with kiss-*. A comment string is optionally usable via setting the second line of the script to a string. Example: ... This also means that 'kiss <script name>' is also possible now. If I have a script in my $PATH called kiss-depends, I can now use it via kiss with 'kiss depends'. 2020-04-18 02:39:37 -06:00			`cat "$(kiss s "$1")/depends" 2>/dev/null`