From: Nicolas Schier <nsc@kernel.org>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Onur Özkan" <work@onurozkan.dev>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
linux-doc@vger.kernel.org, workflows@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
automated-testing@lists.yoctoproject.org
Subject: Re: [PATCH 1/2] scripts: add TOML config to container tool
Date: Fri, 28 Aug 2026 18:29:59 +0200 [thread overview]
Message-ID: <apG3hwaPA8f7SJeI@levanger> (raw)
In-Reply-To: <7d8ba914cd174d716340bb2b88723bef0f330627.1787565460.git.gtucker@gtucker.io>
On Mon, Aug 24, 2026 at 12:05:47PM +0200, Guillaume Tucker wrote:
> Add support for a TOML configuration file to the scripts/container
> tool. This improves user experience by not having to keep passing the
> same command line options all the time or overly relying on built-in
> default values. Include the concept of 'profiles' with different
> named sections in the file to cover various use cases.
>
> Command line options take precedence over the config file, and values
> defined in profile sections take precedence over the default one.
>
> Add a -c option to override the location of the .container.toml config
> file which should otherwise be located in the current working
> directory. If not found, the file is silently ignored as it is not
> strictly required unless the -c option is used.
>
> Add a -p option to choose a particular profile section in the config
> file rather than the default.
>
> Signed-off-by: Guillaume Tucker <gtucker@gtucker.io>
> ---
> scripts/container | 81 ++++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 70 insertions(+), 11 deletions(-)
>
> diff --git a/scripts/container b/scripts/container
> index b05333d8530b..cf126fa13510 100755
> --- a/scripts/container
> +++ b/scripts/container
> @@ -1,17 +1,19 @@
> #!/usr/bin/env python3
> # SPDX-License-Identifier: GPL-2.0-only
> -# Copyright (C) 2025 Guillaume Tucker
> +# Copyright (C) 2025-2026 Guillaume Tucker
>
> """Containerized builds"""
>
> import abc
> import argparse
> +import dataclasses
> import logging
> import os
> import pathlib
> import shutil
> import subprocess
> import sys
> +import tomllib
Have you seen the comment from sashiko?
| Will this unconditional import of tomllib crash the script on startup for
| users running supported Python versions like 3.9 and 3.10?
| The kernel's baseline requirement allows Python 3.9.x, but tomllib is only
| available starting in Python 3.11.
https://sashiko.dev/#/patchset/15e16f175f59ae666036764eb03c40cdf19809c7.1787896890.git.gtucker@gtucker.io
(and there are some others...)
Kind regards,
Nicolas
next prev parent reply other threads:[~2026-08-28 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 10:05 Guillaume Tucker
2026-08-24 10:05 ` [PATCH 2/2] Documentation: dev-tools: update container.rst with config file Guillaume Tucker
2026-08-24 10:55 ` Guillaume Tucker
2026-08-28 6:35 ` Guillaume Tucker
2026-08-28 6:39 ` [PATCH 1/2] scripts: add TOML config to container tool Guillaume Tucker
2026-08-28 16:29 ` Nicolas Schier [this message]
2026-08-28 17:25 ` Guillaume Tucker
2026-08-28 17:35 ` Miguel Ojeda
2026-08-29 8:56 ` Guillaume Tucker
2026-08-29 11:01 ` Miguel Ojeda
2026-08-29 9:02 ` Guillaume Tucker
2026-08-29 10:57 ` Miguel Ojeda
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=apG3hwaPA8f7SJeI@levanger \
--to=nsc@kernel.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=corbet@lwn.net \
--cc=gtucker@gtucker.io \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=work@onurozkan.dev \
--cc=workflows@vger.kernel.org \
/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
all inboxes | Powered by JetHome®