summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Schmaus <flow@gentoo.org>2024-02-29 14:32:18 +0100
committerFlorian Schmaus <flow@gentoo.org>2024-03-01 11:05:29 +0100
commit5fcd6e6c71d0de56a7e77f8fc14f765740384021 (patch)
tree8977cffe6c3f284f7eaec5483ca27e189b2aced6
parenttexlive-module.eclass: implicitly set TL_PV if not explicitly set (diff)
downloadgentoo-5fcd6e6c71d0de56a7e77f8fc14f765740384021.tar.gz
gentoo-5fcd6e6c71d0de56a7e77f8fc14f765740384021.tar.bz2
gentoo-5fcd6e6c71d0de56a7e77f8fc14f765740384021.zip
texlive-common.eclass: check exit status of texmf-update
The texlive eclasses where traditionally lenient when it comes to the exit status of texmf-update and fmtutil-sys, as they would return a non-zero exit status in certain situations, especially when bootstraping the texlive installation, i.e., when texlive-core is installed. With the upcoming Texlive 2023 bbump we can make this more strict, having texlive-core use nonfatal. Signed-off-by: Florian Schmaus <flow@gentoo.org>
-rw-r--r--eclass/texlive-common.eclass4
1 files changed, 4 insertions, 0 deletions
diff --git a/eclass/texlive-common.eclass b/eclass/texlive-common.eclass
index fab6ff66ecd5..f1933b1166f8 100644
--- a/eclass/texlive-common.eclass
+++ b/eclass/texlive-common.eclass
@@ -178,6 +178,10 @@ etexmf-update() {
if has_version 'app-text/texlive-core' ; then
if [[ -z ${ROOT} && -x "${EPREFIX}"/usr/sbin/texmf-update ]] ; then
"${EPREFIX}"/usr/sbin/texmf-update
+ local res="${?}"
+ if [[ "${res}" -ne 0 ]] && ver_test -ge 2023; then
+ die -n "texmf-update returned non-zero exit status ${res}"
+ fi
else
ewarn "Cannot run texmf-update for some reason."
ewarn "Your texmf tree might be inconsistent with your configuration"