[Linux-ha-dev] usage of variables for binaries in ocf resource scripts

[Andrew Beekhof]

On 8/25/07, Sebastian Reitenbach <sebastia at l00-bugdead-prods.de> wrote:
> Hi,
>
> when I take a look into ${OCF_ROOT}/.ocf-binaries I see some definitions
> below that comment line:
> ...
> # Entries that should probably be removed
> : ${BASENAME:=basename}
> : ${BLOCKDEV:=blockdev}
> : ${CAT:=cat}
> : ${FSCK:=fsck}
> ...
>
> are these variables planned to be removed in some future version?

i'd like to but probably can't (if only for legacy reasons)

> should I not use these variables, and expect the binaries available
> somewhere in $PATH?

most are already required to be in the path... usually by POSIX itself

but more to the point, i see no advantage to pointless indirections...
sure some programs have equivalents (yacc, bison etc) but cat is cat.