On 3/27/19 10:39 AM, dueffert--- via blfs-dev wrote:
Another is to not have `&&' at the end of line. Actually, what would
we lose?
The freedom to have failing commands in a script [that e.g. try to
remove files that may not exist] and a way to mark command blocks as
independent...
Sometimes in a script with a pipeline you may want to continue
regardless or errors. In that case running in a subshell:
configure &&
make &&
(make check || true ) &&
make install
will do what you want. Note in the above you probably want to capture
output to a log:
{
configure &&
make &&
(make check || true ) &&
make install
} 2>&1 | tee -a package.log
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
