From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: tex@gentoo.org
Subject: [gentoo-dev] Re: [PATCH] efmtutil-sys: use ebegin/eend and log output
Date: Thu, 4 Apr 2024 15:04:47 +0200 [thread overview]
Message-ID: <0c9c8deb-89f6-4b27-9ee0-6fac5818e5ce@gentoo.org> (raw)
In-Reply-To: <20240404130141.1550223-1-flow@gentoo.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1218 bytes --]
I just noticed two things seconds after sending the patch:
Commit message is missing "texlive-common.eclass" prefix.
On 04/04/2024 15.01, Florian Schmaus wrote:
> Use ebegin/eend and instead of redirecting the output to /dev/null
> capture stdout and stderr under a file under $T.
>
> Signed-off-by: Florian Schmaus <flow@gentoo.org>
> ---
> eclass/texlive-common.eclass | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/eclass/texlive-common.eclass b/eclass/texlive-common.eclass
> index 66d3999bd103..0cc61f735cb2 100644
> --- a/eclass/texlive-common.eclass
> +++ b/eclass/texlive-common.eclass
> @@ -199,9 +199,11 @@ etexmf-update() {
> efmtutil-sys() {
> if has_version 'app-text/texlive-core' ; then
> if [[ -z ${ROOT} && -x "${EPREFIX}"/usr/bin/fmtutil-sys ]] ; then
> - einfo "Rebuilding formats"
> - "${EPREFIX}"/usr/bin/fmtutil-sys --all &> /dev/null ||
> - die -n "fmtutil-sys returned non-zero exit status ${?}"
> + ebegin "Rebuilding TexLive formats"
> + "${EPREFIX}"/usr/bin/fmtutil-sys --all \
> + > "${T}"/fmutil-sys-all.log \
> + &> "${T}"/fmutil-sys-all.err.log
This should be 2> instead of &>
- Flow
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17797 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2024-04-04 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 13:01 [gentoo-dev] [PATCH] efmtutil-sys: use ebegin/eend and log output Florian Schmaus
2024-04-04 13:04 ` Florian Schmaus [this message]
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=0c9c8deb-89f6-4b27-9ee0-6fac5818e5ce@gentoo.org \
--to=flow@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=tex@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