On Tue, Sep 12, 2017 at 9:20 PM, Eduardo Bustamante <dual...@gmail.com> wrote:
> On Tue, Sep 12, 2017 at 5:04 PM, Adam Danischewski > <adam.danischew...@gmail.com> wrote: > [...] > > Declaring a variable doesn't seem risky enough to eat up the return code. > > Is there a reason for this? I doubt that it would break anything to > change. > > It's a lot more intuitive and syntactically streamlined to check for > > missing packages/software at the initial declaration as a sanity check. > > This topic has been discussed several times in the past. Please > review: https://lists.gnu.org/archive/html/bug-bash/2010-03/msg00010.html > and https://lists.gnu.org/archive/html/bug-bash/2010-03/msg00036.html > for an explanation. > > In short, declare foo foo=$(bar) || echo blah Same for local, etc. It's cleaner anyway
