Login
You're viewing the functional.cafe public feed.
  • May 9, 2026, 9:31 AM

    analyzing why #osmocom ARM package building is taking too long: Turns out the build worker is spending 7.5 times more time in post-installation of latex (for setting up the package build) than it is taking to actually build osmo-sgsn including its user manual: osmocom.org/issues/7009

    💬 1🔄 0⭐ 0

Replies

  • May 9, 2026, 9:44 AM

    @LaF0rge these are exactly the reasons GR CI pre-rolls container images and then runs in the container fs (namespace) with LaTeX etc readily installed.
    the MinGW and Conda builds where that isn't done take much longer, because they waste time setting up the same environment over and over again.

    💬 2🔄 0⭐ 0
  • May 9, 2026, 9:52 AM

    @LaF0rge (other than that, the whole "it's normal that indexing a couple hundred directories for the TeX interpreter to later find packages quickly takes minutes" is stupid and reasonable people "should" have fixed that eons ago, but I can't blame any reasonable person for not wanting to work on that tooling.
    (I have similar problems with `mandb` taking long, whereas I don't need that db at all, as my computer can both list the whole manpages tree in ~100 μs as well as full-text search in ms)

    💬 0🔄 0⭐ 0
  • May 10, 2026, 8:08 AM

    @funkylab for CI / Jenkins we're also doing that. But for self-hostes opensuse build system workers workers I think their intentional philosophy is to always start from scratch to make sure the package build environment doesn't contain things that the package doesn't explicitly list as dependency. So we have to deviate from that standard and modify it there.

    💬 1🔄 0⭐ 0
  • May 10, 2026, 8:33 AM

    @LaF0rge if fmtutil/mktexfmt are the main culprit, you can try having a high-priority fmtutil.cnf that disables the generation of most formats (aside from what you probably need for docs purposes); see `man mktexfmt`.

    (generally, really confused why these .fmt files need to be regenerated locally instead of coming as part of the binary package.)

    💬 1🔄 0⭐ 0
  • May 10, 2026, 10:29 AM

    @LaF0rge (I think you could then just roll an RPM with such a config file and otherwise just the generated format files from the build machine (BuildRequires: texlive…, and then just copy files from /var/lib/texmf/web2c/{pdftex,tex,…} . That's a less superficially hacky way of doing a stupid hack. )

    💬 0🔄 0⭐ 0