public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
	<docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 3/5] tools/build-docs-container: add CentOS Stream 9 support
Date: Thu, 11 Dec 2025 09:13:01 +0100	[thread overview]
Message-ID: <DEV8IYRW4N8I.1TU6E77ZW6TBL@bootlin.com> (raw)
In-Reply-To: <7ad37c04-75cc-4389-9cf5-72b49b001f28@cherry.de>

Hi,

On Fri Dec 5, 2025 at 4:29 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 12/5/25 3:51 PM, Antonin Godard via lists.yoctoproject.org wrote:
>
> [...]
>
>> diff --git a/documentation/tools/build-docs-container b/documentation/tools/build-docs-container
>> index 7d25b15b9..d753e2153 100755
>> --- a/documentation/tools/build-docs-container
>> +++ b/documentation/tools/build-docs-container
>> @@ -41,6 +41,7 @@ $0 OCI_IMAGE [make arguments...]
>>        - fedora:42
>>        - leap:15.5
>>        - leap:15.6
>> +     - tgagor/centos:stream9
>
> quay.io/centos/centos:stream9 is probably better?
>
> We would need to remove the docker.io prefix from the ARG_FROM and make 
> it configurable but that should be easy to do.

Indeed, I'll do that thanks.

>> diff --git a/documentation/tools/containerfiles/entrypoint b/documentation/tools/containerfiles/entrypoint
>> new file mode 100644
>> index 000000000..97ee93c29
>> --- /dev/null
>> +++ b/documentation/tools/containerfiles/entrypoint
>> @@ -0,0 +1,6 @@
>> +#!/usr/bin/env sh
>> +
>> +tldir=/opt/docs-build-tex-tools/tl/bin/x86_64-linux
>> +[ -d $tldir ] && export PATH="$PATH:$tldir"
>> +
>> +make -C documentation/ "$@"
>
> Doesn't
>
> ENV PATH="$PATH:$TEXTOOLDIR/tl/bin/x86_64-linux"
>
> in Containerfile.stream work just fine instead of having to go through 
> an ENTRYPOINT?

Works nicely! That will allow some simplifications, thanks.

> This also makes the instructions x86_64-only. I have no clue if one can 
> run the current instructions on Aarch64 and make it work, but this for 
> sure won't help.

Yeah correct, well I will add a warning for that, as I don't think I'll have the
time to add support for other archs or if even possible with this installer.

>> diff --git a/documentation/tools/host_packages_scripts/centosstream_docs.sh b/documentation/tools/host_packages_scripts/centosstream_docs.sh
>> new file mode 100644
>> index 000000000..9202afc5b
>> --- /dev/null
>> +++ b/documentation/tools/host_packages_scripts/centosstream_docs.sh
>> @@ -0,0 +1 @@
>> +sudo dnf install -y git glibc-locale-source librsvg2-tools make python3-pip which
>> diff --git a/documentation/tools/host_packages_scripts/centosstream_essential.sh b/documentation/tools/host_packages_scripts/centosstream_essential.sh
>> new file mode 100644
>> index 000000000..e38fa93c2
>> --- /dev/null
>> +++ b/documentation/tools/host_packages_scripts/centosstream_essential.sh
>> @@ -0,0 +1,5 @@
>> +sudo dnf install -y epel-release
>> +sudo yum install -y dnf-plugins-core
>> +sudo dnf config-manager --set-enabled crb
>> +sudo dnf makecache
>> +sudo dnf install -y bzip2 ccache chrpath cpio cpp diffstat diffutils gawk gcc gcc-c++ git glibc-devel glibc-langpack-en gzip libacl make patch perl perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue python3 python3-GitPython python3-jinja2 python3-pexpect python3-pip rpcgen socat tar texinfo unzip wget which xz zstd
>> diff --git a/documentation/tools/host_packages_scripts/tlmgr_docs_pdf.sh b/documentation/tools/host_packages_scripts/tlmgr_docs_pdf.sh
>> new file mode 100644
>> index 000000000..f3b81da3e
>> --- /dev/null
>> +++ b/documentation/tools/host_packages_scripts/tlmgr_docs_pdf.sh
>> @@ -0,0 +1,7 @@
>> +textooldir=${TEXTOOLDIR:-"./docs-build-tex-tools"}
>> +mkdir -p "$textooldir"/tl
>> +wget https://mirror.ctan.org/systems/texlive/tlnet/install-tl-unx.tar.gz -O "$textooldir"/install-tl-unx.tar.gz
>> +zcat < "$textooldir"/install-tl-unx.tar.gz | tar xf - -C "$textooldir"
>
> Can't this simply be
>
> tar xzf "$textooldir"/install-tl-unx.tar.gz -C "$textooldir"

It can! Thanks.

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-12-11  8:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 14:51 [PATCH 0/5] Add missing CentOS Stream / RockyLinux distros to the system-requirements.rst doc Antonin Godard
2025-12-05 14:51 ` [PATCH 1/5] tools/build-docs-container: move container files in their own directory Antonin Godard
2025-12-05 14:51 ` [PATCH 2/5] Makefile: fix rsvg-convert --format capitalization Antonin Godard
2025-12-05 15:03   ` [docs] " Quentin Schulz
2025-12-05 14:51 ` [PATCH 3/5] tools/build-docs-container: add CentOS Stream 9 support Antonin Godard
2025-12-05 15:29   ` [docs] " Quentin Schulz
2025-12-11  8:13     ` Antonin Godard [this message]
2025-12-05 14:51 ` [PATCH 4/5] ref-manual/system-requirements.rst: fix AlmaLinux PDF build Antonin Godard
2025-12-05 14:51 ` [PATCH 5/5] ref-manual/system-requirements.rst: add RockyLinux install instructions Antonin Godard

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=DEV8IYRW4N8I.1TU6E77ZW6TBL@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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