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 v2 1/5] tools/build-docs-container: move container files in their own directory
Date: Fri, 12 Dec 2025 09:19:08 +0100	[thread overview]
Message-ID: <DEW3A6LDZ6KZ.196SQHDYBEC4A@bootlin.com> (raw)
In-Reply-To: <b6c3573d-91f1-4635-b77f-c6daa1a7b0db@cherry.de>

Hi,

On Thu Dec 11, 2025 at 1:26 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 12/11/25 10:06 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> Create a directory to hold the Containerfiles as they were lying next to
>> the scripts. Change the build context of the docker build command to
>> build from SCRIPT_DIR and pass the host packages scripts and container
>> file relative to it.
>> 
>
> It's unclear what this helps with. (I'm assuming this could be a remnant 
> from last version's ENTRYPOINT support attempt?).

It's just for re-organizing, serves no other purpose than not mixing up scripts
and container files.

>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>>   documentation/tools/build-docs-container                    | 13 ++++++-------
>>   .../tools/{ => containerfiles}/Containerfile.almalinux      |  0
>>   documentation/tools/{ => containerfiles}/Containerfile.apt  |  0
>>   .../tools/{ => containerfiles}/Containerfile.debian         |  0
>>   documentation/tools/{ => containerfiles}/Containerfile.dnf  |  0
>>   .../tools/{ => containerfiles}/Containerfile.fedora         |  0
>>   .../tools/{ => containerfiles}/Containerfile.ubuntu         |  0
>>   .../tools/{ => containerfiles}/Containerfile.zypper         |  0
>>   8 files changed, 6 insertions(+), 7 deletions(-)
>> 
>> diff --git a/documentation/tools/build-docs-container b/documentation/tools/build-docs-container
>> index b91a6daa9..7d25b15b9 100755
>> --- a/documentation/tools/build-docs-container
>> +++ b/documentation/tools/build-docs-container
>> @@ -23,7 +23,6 @@ set -eu -o pipefail
>>   SCRIPT_DIR=$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" &>/dev/null && pwd)
>>   CONTAINERCMD=${CONTAINERCMD:-docker}
>>   DOCS_DIR="$SCRIPT_DIR/../.."
>> -SH_DIR="$SCRIPT_DIR/host_packages_scripts"
>>   INCLUDE_ESSENTIAL_PACKAGES=${INCLUDE_ESSENTIAL_PACKAGES:-0}
>>   
>>   function usage()
>> @@ -140,12 +139,12 @@ main ()
>>       --tag "yocto-docs-$sanitized_dockername:latest" \
>>       --build-arg ARG_FROM="docker.io/$image" \
>>       --build-arg INCLUDE_ESSENTIAL_PACKAGES="${INCLUDE_ESSENTIAL_PACKAGES}" \
>> -    --build-arg ESSENTIAL="$essential" \
>> -    --build-arg DOCS="$docs" \
>> -    --build-arg DOCS_PDF="$docs_pdf" \
>> -    --build-arg PIP3="${pip3:-}" \
>> -    --file "$SCRIPT_DIR/$containerfile" \
>> -    "$SH_DIR/"
>> +    --build-arg ESSENTIAL="host_packages_scripts/$essential" \
>> +    --build-arg DOCS="host_packages_scripts/$docs" \
>> +    --build-arg DOCS_PDF="host_packages_scripts/$docs_pdf" \
>> +    --build-arg PIP3="host_packages_scripts/${pip3:-}" \
>> +    --file "$SCRIPT_DIR/containerfiles/$containerfile" \
>> +    "$SCRIPT_DIR"
>>   
>
> This seems to be doing two things: moving Containerfile.* into a subdir 
> containerfiles and changing the context dir from SH_DIR to SCRIPT_DIR. 
> Is there a reason they are both done in the same commit? Is the latter 
> really necessary (I'm not sure it helps in terms of readability?).

I wasn't able to make that work any other way.

Antonin

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



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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11  9:06 [PATCH v2 0/5] Add missing CentOS Stream / RockyLinux distros to the system-requirements.rst doc Antonin Godard
2025-12-11  9:06 ` [PATCH v2 1/5] tools/build-docs-container: move container files in their own directory Antonin Godard
2025-12-11 12:26   ` [docs] " Quentin Schulz
2025-12-12  8:19     ` Antonin Godard [this message]
2025-12-11  9:06 ` [PATCH v2 2/5] Makefile: fix rsvg-convert --format capitalization Antonin Godard
2025-12-11 12:27   ` [docs] " Quentin Schulz
2025-12-11  9:06 ` [PATCH v2 3/5] tools/build-docs-container: add CentOS Stream 9 support Antonin Godard
2025-12-11 12:43   ` [docs] " Quentin Schulz
2025-12-11  9:06 ` [PATCH v2 4/5] ref-manual/system-requirements.rst: fix AlmaLinux PDF build Antonin Godard
2025-12-11 13:55   ` [docs] " Quentin Schulz
2025-12-11  9:06 ` [PATCH v2 5/5] ref-manual/system-requirements.rst: add RockyLinux install instructions Antonin Godard
2025-12-11 13:59   ` [docs] " Quentin Schulz
2026-01-05 13:52 ` [PATCH v2 0/5] Add missing CentOS Stream / RockyLinux distros to the system-requirements.rst doc 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=DEW3A6LDZ6KZ.196SQHDYBEC4A@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