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] [yocto-docs PATCH 1/5] Gather dependencies in poky.yaml.in
Date: Fri, 29 Nov 2024 15:06:20 +0100 [thread overview]
Message-ID: <D5YPY3NDWDHV.RWVHIE7HDBFR@bootlin.com> (raw)
In-Reply-To: <86bd7352-1a33-492d-8308-c2eeff6b4a71@cherry.de>
Hi Quentin,
On Mon Nov 25, 2024 at 6:55 PM CET, Quentin Schulz wrote:
[...]
>> diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst
>> index b33518c7f1e0c76caa70a719e023b9c405b744e2..ca75f849d0ad10344900c7525f7163726ffe5400 100644
>> --- a/documentation/ref-manual/system-requirements.rst
>> +++ b/documentation/ref-manual/system-requirements.rst
>> @@ -150,7 +150,7 @@ Ubuntu and Debian
>> Here are the packages needed to build an image on a headless system
>> with a supported Ubuntu or Debian Linux distribution::
>>
>> - $ sudo apt install &UBUNTU_HOST_PACKAGES_ESSENTIAL;
>> + $ sudo apt install &UBUNTU_DEBIAN_HOST_PACKAGES_ESSENTIAL;
>>
>> You also need to ensure you have the locale ``en_US.UTF-8`` enabled::
>>
>> @@ -172,8 +172,7 @@ If this is not the case, you can reconfigure the ``locales`` package to add it::
>>
>> Here are the packages needed to build Project documentation manuals::
>>
>> - $ sudo apt install git make inkscape texlive-latex-extra
>> - $ sudo apt install sphinx python3-saneyaml python3-sphinx-rtd-theme
>> + $ sudo apt install &UBUNTU_DEBIAN_HOST_PACKAGES_DOC;
>
> Aren't we missing the PIP3_HOST_PACKAGES_DOC here?
>
> Also FYI, using pip on the system level is a very bad practice (as a
> matter of fact, it's not even allowed on Debian Bookworm anymore). We
> should probably rather document how to do this in virtual environments
> for example? One thing after the other though, we can start by just
> migrating the docs variable for now :)
Yeah, I am aware it's terrible practice and we shouldn't do that. I'd also
recommend using virtualenvs. I'll take a note of this, and try to send a patch
soon! :)
>>
>> Fedora Packages
>> ---------------
>> @@ -185,8 +184,8 @@ with a supported Fedora Linux distribution::
>>
>> Here are the packages needed to build Project documentation manuals::
>>
>> - $ sudo dnf install git make python3-pip which inkscape texlive-fncychap
>> - &PIP3_HOST_PACKAGES_DOC;
>> + $ sudo dnf install &FEDORA_HOST_PACKAGES_DOC;
>> + $ sudo pip3 install &PIP3_HOST_PACKAGES_DOC;
>>
>> openSUSE Packages
>> -----------------
>> @@ -195,11 +194,12 @@ Here are the packages needed to build an image on a headless system
>> with a supported openSUSE distribution::
>>
>> $ sudo zypper install &OPENSUSE_HOST_PACKAGES_ESSENTIAL;
>> + $ sudo pip3 install &OPENSUSE_PIP3_HOST_PACKAGES_ESSENTIAL;
>>
>> Here are the packages needed to build Project documentation manuals::
>>
>> - $ sudo zypper install git make python3-pip which inkscape texlive-fncychap
>> - &PIP3_HOST_PACKAGES_DOC;
>> + $ sudo zypper install &OPENSUSE_HOST_PACKAGES_DOC;
>> + $ sudo pip3 install &PIP3_HOST_PACKAGES_DOC;
>>
>>
>> AlmaLinux Packages
>> @@ -208,7 +208,7 @@ AlmaLinux Packages
>> Here are the packages needed to build an image on a headless system
>> with a supported AlmaLinux distribution::
>>
>> - $ sudo dnf install &ALMALINUX_HOST_PACKAGES_ESSENTIAL;
>> +&ALMALINUX_HOST_PACKAGES_ESSENTIAL_CMDS;
>
> It's a bit odd to have a different way to add the packages to install
> depending on the distro, couldn't we have all distros have no
> indentation, or all have some indentation?
That's the only exception, because Alma Linux has several installation steps.
I'd rather keep only the dependency lists in poky.yaml.in, so I'll add the
commands back here, and use ALMALINUX_HOST_PACKAGES_ESSENTIAL in the rst doc
instead (just like what's done for the other distros).
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-11-29 14:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 15:10 [yocto-docs PATCH 0/5] Update the dependencies in poky.yaml.in Antonin Godard
2024-11-20 15:10 ` [yocto-docs PATCH 1/5] Gather " Antonin Godard
2024-11-25 17:55 ` [docs] " Quentin Schulz
2024-11-29 14:06 ` Antonin Godard [this message]
2024-11-20 15:10 ` [yocto-docs PATCH 2/5] poky.yaml.in: replace inkscape dependency by librsvg2-bin Antonin Godard
2024-11-25 17:58 ` [docs] " Quentin Schulz
2024-11-29 14:06 ` Antonin Godard
2024-11-20 15:10 ` [yocto-docs PATCH 3/5] system-requirements: update list of supported distros Antonin Godard
2024-11-25 18:04 ` [docs] " Quentin Schulz
2024-11-29 14:06 ` Antonin Godard
2024-11-20 15:10 ` [yocto-docs PATCH 4/5] system-requirements.rst: add dependencies for pdf builds Antonin Godard
2024-11-25 18:11 ` [docs] " Quentin Schulz
2024-11-29 14:06 ` Antonin Godard
2024-11-29 14:28 ` Quentin Schulz
2024-11-29 15:21 ` Antonin Godard
2024-11-20 15:10 ` [yocto-docs PATCH 5/5] poky.yaml.in: add missing locales dependency Antonin Godard
2024-11-25 18:12 ` [docs] " Quentin Schulz
2024-11-29 14:06 ` 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=D5YPY3NDWDHV.RWVHIE7HDBFR@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