Re: [docs] [PATCH RFC v2 2/2] tools: add script for building documentation inside containers

["Antonin Godard" <antonin.godard@bootlin.com>]

Hi Quentin,

On Mon Jan 13, 2025 at 5:43 PM CET, Quentin Schulz wrote:
[...]
>>> +# relative to the location of the dockerfile
>>> +COPY --chmod=777 ${DOCS} /temp/host_packages_docs.sh
>>> +COPY --chmod=777 ${DOCS_PDF} /temp/host_packages_docs_pdf.sh
>>> +COPY --chmod=777 ${PIP3} /temp/pip3_docs.sh
>> 
>> A bit of a hacky workaround, but maybe here run
>> sed -i 's/zypper/zypper --non-interactive/ ...' on the scripts? So we don't need
>> to provide this option in the doc.
>> 
>
> Another dirty hack is to have a shell zypper wrapper that calls 
> /usr/bin/zypper --non-interactive.
>
> Up to you.

Let's go for a sed in the Containerfile.

[...]
>> 
>> Can we have a way of listing images here so a user doesn't need to read the
>> script and guess which one to use?
>> 
>
> The ones in 
> https://docs.yoctoproject.org/ref-manual/system-requirements.html#supported-linux-distributions? 
> Though I guess Rocky and CentOS are still missing. Do we want the name 
> of the distro or the name + the version? Basically we can end up with 
> two places where this information will be, in the docs and in the container.

I was thinking of just listing what the script supports, not from the docs. I
did that in my version of the script. Something like `./build-docs-container
list`. In your case, it would probably extract that information from the
Containerfiles.

Antonin

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