From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Vincent Jardin via buildroot <buildroot@buildroot.org>
Cc: Vincent Jardin <vjardin@free.fr>
Subject: Re: [Buildroot] [PATCH v1 1/2] package/python-libyang: new package
Date: Wed, 7 Jan 2026 23:40:58 +0100 [thread overview]
Message-ID: <20260107234058.5c46e3aa@windsurf> (raw)
In-Reply-To: <20260107175446.2470125-2-vjardin@free.fr>
Hello Vincent,
On Wed, 7 Jan 2026 18:54:45 +0100
Vincent Jardin via buildroot <buildroot@buildroot.org> wrote:
> diff --git a/DEVELOPERS b/DEVELOPERS
> index f982e3123a..5585e8b353 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -3359,6 +3359,8 @@ F: package/bfscripts/
> F: package/dpdk/
> F: package/libecoli/
> F: package/libyang-cpp/
> +F: package/python-libyang/
> +F: package/python-sysrepo/
There's a problem in the patch splitting here. This patch should only
add the entry for python-libyang.
> F: package/sysrepo-cpp/
>
> N: Vincent Prince <vincent.prince.fr@gmail.com>
> diff --git a/package/Config.in b/package/Config.in
> index def3db0e50..19d32c16ea 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -1205,6 +1205,7 @@ menu "External python modules"
> source "package/python-libconfig/Config.in"
> source "package/python-libevdev/Config.in"
> source "package/python-libusb1/Config.in"
> + source "package/python-libyang/Config.in"
> source "package/python-lmdb/Config.in"
> source "package/python-lockfile/Config.in"
> source "package/python-log-rate-limit/Config.in"
> @@ -1434,6 +1435,7 @@ menu "External python modules"
> source "package/python-stack-data/Config.in"
> source "package/python-starlette/Config.in"
> source "package/python-sympy/Config.in"
> + source "package/python-sysrepo/Config.in"
> source "package/python-systemd/Config.in"
> source "package/python-tabledata/Config.in"
> source "package/python-tcolorpy/Config.in"
Same comment here.
> diff --git a/package/python-libyang/Config.in b/package/python-libyang/Config.in
> new file mode 100644
> index 0000000000..793bf7e3c5
> --- /dev/null
> +++ b/package/python-libyang/Config.in
> @@ -0,0 +1,23 @@
> +config BR2_PACKAGE_PYTHON_LIBYANG
> + bool "python-libyang"
> + depends on BR2_PACKAGE_PYTHON3
Not needed, since all python-*/Config.in are already included inside a
if BR2_PACKAGE_PYTHON3... endif condition.
> + depends on BR2_PACKAGE_LIBYANG
This should be a "select", and then you replicate the "depends on" from
BR2_PACKAGE_LIBYANG:
depends on BR2_TOOLCHAIN_HAS_SYNC_4 # libyang
depends on BR2_TOOLCHAIN_HAS_THREADS # libyang
depends on !BR2_STATIC_LIBS # libyang
> + # Python3 doesn't work with uClibc and kernel headers < 5.1
> + depends on !BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1
This is no longer the case, this issue has been fixed in Buildroot, so
this dependency can be dropped.
> + select BR2_PACKAGE_PYTHON_CFFI
select BR2_PACKAGE_PYTHON_CFFI # runtime
> + help
> + Python CFFI bindings for the libyang YANG library.
> +
> + This package provides the 'libyang' Python module, used by
> + higher-level tooling such as python-sysrepo.
> +
> + https://github.com/CESNET/libyang-python
> +
> +comment "python-libyang needs python3, uClibc needs kernel headers >= 5.1"
> + depends on !BR2_PACKAGE_PYTHON3 || \
> + (BR2_TOOLCHAIN_USES_UCLIBC && !BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1)
> +
> +comment "python-libyang needs libyang"
> + depends on BR2_PACKAGE_PYTHON3
> + depends on !BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1
> + depends on !BR2_PACKAGE_LIBYANG
This needs to be updated to cover those dependencies:
depends on BR2_TOOLCHAIN_HAS_SYNC_4 # libyang
depends on BR2_TOOLCHAIN_HAS_THREADS # libyang
depends on !BR2_STATIC_LIBS # libyang
No need to mention the python3 dependency.
Rest looks good to me.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-07 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 17:54 [Buildroot] [PATCH v1 0/2] Add python-libyang and python-sysrepo packages Vincent Jardin via buildroot
2026-01-07 17:54 ` [Buildroot] [PATCH v1 1/2] package/python-libyang: new package Vincent Jardin via buildroot
2026-01-07 22:40 ` Thomas Petazzoni via buildroot [this message]
2026-01-07 17:54 ` [Buildroot] [PATCH v1 2/2] package/python-sysrepo: " Vincent Jardin via buildroot
2026-01-07 22:45 ` Thomas Petazzoni via buildroot
2026-01-18 21:31 ` [Buildroot] [PATCH v1 0/1] package/sysrepo: fix build on riscv32 Vincent Jardin via buildroot
2026-01-18 21:31 ` [Buildroot] [PATCH v1 1/1] " Vincent Jardin via buildroot
2026-01-18 21:51 ` Thomas Petazzoni via buildroot
2026-02-17 16:00 ` [Buildroot] [PATCH v2 " Vincent Cruz
2026-02-18 12:31 ` mooz
2026-01-18 21:51 ` [Buildroot] [PATCH v1 0/1] " Thomas Petazzoni via buildroot
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=20260107234058.5c46e3aa@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vjardin@free.fr \
/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