From: "Alexander Kurakin" <kuraga333@mail.ru>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] .ebuild-Bash-scripts and (non-)fatal errors
Date: Wed, 01 Feb 2023 22:25:57 +0300 [thread overview]
Message-ID: <1675279557.92897956@f110.i.mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
Good day!
What are the reasons why `.ebuild`-Bash-scripts are started by `emerge`/etc. without `set -e` flag?
In other words, `QA Notice: command not found` is just a QA notice instead of a fatal error.
And can I change it for some `emerge` run?
Sincerely,
Alexander Kurakin.
[-- Attachment #2: Type: text/html, Size: 480 bytes --]
reply other threads:[~2023-02-01 19:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1675279557.92897956@f110.i.mail.ru \
--to=kuraga333@mail.ru \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox