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 2/2] ref-manual/system-requirements.rst: instruct to install a buildtools tarball
Date: Mon, 20 Apr 2026 12:54:58 +0200	[thread overview]
Message-ID: <DHXXDS128COZ.35MAUIPGK4G1Y@bootlin.com> (raw)
In-Reply-To: <e74cbdf2-7a0c-4d0d-aa77-c67823aa2e54@cherry.de>

Hi,

On Mon Apr 20, 2026 at 12:46 PM CEST, Quentin Schulz wrote:
> Hi Antonin,
>
> On 4/20/26 11:52 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> I noticed that openSUSE Leap 15.6 provide Python 3.6, which is not
>> supported by BitBake (which requires Python >3.9). Instruct to use a
>> buildtools tarball, which is how this is done on the Autobuilder.
>> 
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>>   documentation/ref-manual/system-requirements.rst | 5 +++++
>>   1 file changed, 5 insertions(+)
>> 
>> diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst
>> index baa965573..85a26060c 100644
>> --- a/documentation/ref-manual/system-requirements.rst
>> +++ b/documentation/ref-manual/system-requirements.rst
>> @@ -243,6 +243,11 @@ with a supported openSUSE Leap 15.6 distribution:
>>   .. literalinclude:: ../tools/host_packages_scripts/opensuse_essential_15.6.sh
>>      :language: shell
>>   
>> +Additionally, openSUSE Leap 15.6 requires a :term:`buildtools` tarball to be
>> +installed and set up, as this distribution provides a version of Python that is
>> +too old for :term:`BitBake`. Follow the :ref:`system-requirements-buildtools`
>> +section below for more information.
>> +
>
> Shouldn't the buildtools cover all required packages to be present on 
> the host? If so, do we actually need instructions without (e.g. the 
> opensuse_essential_15.6.sh above)?

Probably, but to be fair I'm trying to match what is installed on the
Autobuilder (and that is known to work), and I'd like to avoid dropping one
requirement by mistake. That's a bit inefficient, but a bit safer. I wish the
Autobuilder list of requirements was public and allow my to test things but I
don't have such an environment :/

Antonin


      reply	other threads:[~2026-04-20 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20  9:52 [PATCH v2 0/2] Updates to host requirements Antonin Godard
2026-04-20  9:52 ` [PATCH v2 1/2] ref-manual/system-requirements.rst: make python3-websockets a default host requirement Antonin Godard
2026-04-20 10:43   ` [docs] " Quentin Schulz
2026-04-20 10:59     ` Antonin Godard
2026-04-20  9:52 ` [PATCH v2 2/2] ref-manual/system-requirements.rst: instruct to install a buildtools tarball Antonin Godard
2026-04-20 10:46   ` [docs] " Quentin Schulz
2026-04-20 10:54     ` Antonin Godard [this message]

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=DHXXDS128COZ.35MAUIPGK4G1Y@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