From: Quentin Schulz <quentin.schulz@cherry.de>
To: rpjday@crashcourse.ca,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] should YP docs host_packages_scripts have symlinks for debian?
Date: Wed, 7 Jan 2026 14:05:49 +0100 [thread overview]
Message-ID: <4f795aef-9432-448d-a21f-e1be7b09768e@cherry.de> (raw)
In-Reply-To: <64f61085-723b-70d5-a019-f11c02e8c8b2@crashcourse.ca>
Hi Robert,
On 1/6/26 9:45 PM, Robert P. J. Day via lists.yoctoproject.org wrote:
>
> i noticed when updating my yocto-docs checkout and trying to build
> on debian 13 that i was missing the debian package
> python3-sphinx-copybutton. fair enough, but in the
> host_packages_scripts directory:
>
> https://git.yoctoproject.org/yocto-docs/tree/documentation/tools/host_packages_scripts
>
> there is no explicit debian_docs.sh script, while there are symlinks
> for other distros to cover the bases.
>
> would it make sense for there to be actual debian-flavoured host
> package scripts, and symlinks for debian-derived distros? so the
> debian scripts would be the *actual* scripts, and the ubuntu versions
> would be symlinks? for consistency.
>
Well... The thing is that each separate file is included by the docs for
the respective distro installation steps. Ubuntu and Debian share the
same instructions so they share the same file.
The files in documentation/tools aren't really for outside consumption.
Check from the docs directly (where the instructions would be there and
if outdated must be updated) or use the container for building the docs
(documentation/tools/build-docs-container <container-image> <make
command>, which use the proper file automatically).
Cheers,
Quentin
prev parent reply other threads:[~2026-01-07 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 20:48 should YP docs host_packages_scripts have symlinks for debian? Robert P. J. Day
2026-01-07 13:05 ` Quentin Schulz [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=4f795aef-9432-448d-a21f-e1be7b09768e@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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