[Buildroot] [PATCH 1/3] package/python-annotated-types: new package

[Buildroot] [PATCH 1/3] package/python-annotated-types: new package

[James Hilliard]

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
 package/Config.in                                 |  1 +
 package/python-annotated-types/Config.in          |  6 ++++++
 .../python-annotated-types.hash                   |  5 +++++
 .../python-annotated-types.mk                     | 15 +++++++++++++++
 4 files changed, 27 insertions(+)
 create mode 100644 package/python-annotated-types/Config.in
 create mode 100644 package/python-annotated-types/python-annotated-types.hash
 create mode 100644 package/python-annotated-types/python-annotated-types.mk

diff --git a/package/Config.in b/package/Config.in
index 5a3410d758..68e6e29a4d 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -974,6 +974,7 @@ menu "External python modules"
 	source "package/python-aiozipkin/Config.in"
 	source "package/python-alembic/Config.in"
 	source "package/python-alsaaudio/Config.in"
+	source "package/python-annotated-types/Config.in"
 	source "package/python-ansicolors/Config.in"
 	source "package/python-apispec/Config.in"
 	source "package/python-appdirs/Config.in"
diff --git a/package/python-annotated-types/Config.in b/package/python-annotated-types/Config.in
new file mode 100644
index 0000000000..36525a526b
--- /dev/null
+++ b/package/python-annotated-types/Config.in
@@ -0,0 +1,6 @@
+config BR2_PACKAGE_PYTHON_ANNOTATED_TYPES
+	bool "python-annotated-types"
+	help
+	  Reusable constraint types to use with typing.Annotated.
+
+	  https://github.com/annotated-types/annotated-types
diff --git a/package/python-annotated-types/python-annotated-types.hash b/package/python-annotated-types/python-annotated-types.hash
new file mode 100644
index 0000000000..1663bcb51f
--- /dev/null
+++ b/package/python-annotated-types/python-annotated-types.hash
@@ -0,0 +1,5 @@
+# md5, sha256 from https://pypi.org/pypi/annotated-types/json
+md5  5fe2125b08851f0d05a8efad6456861c  annotated_types-0.6.0.tar.gz
+sha256  563339e807e53ffd9c267e99fc6d9ea23eb8443c08f112651963e24e22f84a5d  annotated_types-0.6.0.tar.gz
+# Locally computed sha256 checksums
+sha256  fe1049884b1a0d9342901e88e07f32925d24b3121d9972b6a6805fb9824b095d  LICENSE
diff --git a/package/python-annotated-types/python-annotated-types.mk b/package/python-annotated-types/python-annotated-types.mk
new file mode 100644
index 0000000000..8bc617069d
--- /dev/null
+++ b/package/python-annotated-types/python-annotated-types.mk
@@ -0,0 +1,15 @@
+################################################################################
+#
+# python-annotated-types
+#
+################################################################################
+
+PYTHON_ANNOTATED_TYPES_VERSION = 0.6.0
+PYTHON_ANNOTATED_TYPES_SOURCE = annotated_types-$(PYTHON_ANNOTATED_TYPES_VERSION).tar.gz
+PYTHON_ANNOTATED_TYPES_SITE = https://files.pythonhosted.org/packages/67/fe/8c7b275824c6d2cd17c93ee85d0ee81c090285b6d52f4876ccc47cf9c3c4
+PYTHON_ANNOTATED_TYPES_SETUP_TYPE = pep517
+PYTHON_ANNOTATED_TYPES_LICENSE = MIT
+PYTHON_ANNOTATED_TYPES_LICENSE_FILES = LICENSE
+PYTHON_ANNOTATED_TYPES_DEPENDENCIES = host-python-hatchling
+
+$(eval $(python-package))
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

[Buildroot] [PATCH 2/3] package/python-pydantic-core: new package

[James Hilliard]

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
 package/Config.in                                 |  1 +
 package/python-pydantic-core/Config.in            |  8 ++++++++
 .../python-pydantic-core.hash                     |  4 ++++
 .../python-pydantic-core/python-pydantic-core.mk  | 15 +++++++++++++++
 4 files changed, 28 insertions(+)
 create mode 100644 package/python-pydantic-core/Config.in
 create mode 100644 package/python-pydantic-core/python-pydantic-core.hash
 create mode 100644 package/python-pydantic-core/python-pydantic-core.mk

diff --git a/package/Config.in b/package/Config.in
index 68e6e29a4d..fcc09b07c4 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -1228,6 +1228,7 @@ menu "External python modules"
 	source "package/python-pycups/Config.in"
 	source "package/python-pydal/Config.in"
 	source "package/python-pydantic/Config.in"
+	source "package/python-pydantic-core/Config.in"
 	source "package/python-pydevmem/Config.in"
 	source "package/python-pydyf/Config.in"
 	source "package/python-pyelftools/Config.in"
diff --git a/package/python-pydantic-core/Config.in b/package/python-pydantic-core/Config.in
new file mode 100644
index 0000000000..3eeb1844a2
--- /dev/null
+++ b/package/python-pydantic-core/Config.in
@@ -0,0 +1,8 @@
+config BR2_PACKAGE_PYTHON_PYDANTIC_CORE
+	bool "python-pydantic-core"
+	depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
+	select BR2_PACKAGE_PYTHON_TYPING_EXTENSIONS # runtime
+	help
+	  Core validation logic for pydantic written in rust.
+
+	  https://github.com/pydantic/pydantic-core
diff --git a/package/python-pydantic-core/python-pydantic-core.hash b/package/python-pydantic-core/python-pydantic-core.hash
new file mode 100644
index 0000000000..4927d816be
--- /dev/null
+++ b/package/python-pydantic-core/python-pydantic-core.hash
@@ -0,0 +1,4 @@
+# Locally calculated after vendoring
+sha256  b54296f8317e7ffd72726836636aa3a6c8c977d8f73b68253c443c0fe3731064  pydantic_core-2.14.5.tar.gz
+# Locally computed sha256 checksums
+sha256  2afdd30d54b4d62b6f488a6bcc1546e84ec5061f13f4209c03d012348783795a  LICENSE
diff --git a/package/python-pydantic-core/python-pydantic-core.mk b/package/python-pydantic-core/python-pydantic-core.mk
new file mode 100644
index 0000000000..8b61323ab3
--- /dev/null
+++ b/package/python-pydantic-core/python-pydantic-core.mk
@@ -0,0 +1,15 @@
+################################################################################
+#
+# python-pydantic-core
+#
+################################################################################
+
+PYTHON_PYDANTIC_CORE_VERSION = 2.14.5
+PYTHON_PYDANTIC_CORE_SOURCE = pydantic_core-$(PYTHON_PYDANTIC_CORE_VERSION).tar.gz
+PYTHON_PYDANTIC_CORE_SITE = https://files.pythonhosted.org/packages/64/26/cffb93fe9c6b5a91c497f37fae14a4b073ecbc47fc36a9979c7aa888b245
+PYTHON_PYDANTIC_CORE_SETUP_TYPE = maturin
+PYTHON_PYDANTIC_CORE_LICENSE = MIT
+PYTHON_PYDANTIC_CORE_LICENSE_FILES = LICENSE
+PYTHON_PYDANTIC_CORE_DEPENDENCIES = host-python-typing-extensions
+
+$(eval $(python-package))
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: new package

[Yann E. MORIN]

James, All,

On 2023-11-25 01:10 -0700, James Hilliard spake thusly:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
>  package/Config.in                                 |  1 +
>  package/python-pydantic-core/Config.in            |  8 ++++++++
>  .../python-pydantic-core.hash                     |  4 ++++
>  .../python-pydantic-core/python-pydantic-core.mk  | 15 +++++++++++++++
>  4 files changed, 28 insertions(+)
>  create mode 100644 package/python-pydantic-core/Config.in
>  create mode 100644 package/python-pydantic-core/python-pydantic-core.hash
>  create mode 100644 package/python-pydantic-core/python-pydantic-core.mk
> 
> diff --git a/package/Config.in b/package/Config.in
> index 68e6e29a4d..fcc09b07c4 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -1228,6 +1228,7 @@ menu "External python modules"
>  	source "package/python-pycups/Config.in"
>  	source "package/python-pydal/Config.in"
>  	source "package/python-pydantic/Config.in"
> +	source "package/python-pydantic-core/Config.in"
>  	source "package/python-pydevmem/Config.in"
>  	source "package/python-pydyf/Config.in"
>  	source "package/python-pyelftools/Config.in"
> diff --git a/package/python-pydantic-core/Config.in b/package/python-pydantic-core/Config.in
> new file mode 100644
> index 0000000000..3eeb1844a2
> --- /dev/null
> +++ b/package/python-pydantic-core/Config.in
> @@ -0,0 +1,8 @@
> +config BR2_PACKAGE_PYTHON_PYDANTIC_CORE
> +	bool "python-pydantic-core"
> +	depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
> +	select BR2_PACKAGE_PYTHON_TYPING_EXTENSIONS # runtime
> +	help

So what happens if I apply this patch, which adds pydantic-core, but I
do not apply the next one, which bumps pydantic, so we end up in a
situation with an old pydantic, with the new core also installed?

Do the two conflict, or is it an OK situation (obviously the
pydantic-core would be of little use)?

If there is a conflict, then we will want to introduce the new package
at the same time we do the bump, and that should be explained int he
commit log.

If there is no conflict, then just say, we can ammend the commit log
accordignly.

> +	  Core validation logic for pydantic written in rust.

As it is written in rust, I was wondering... [0]

[--SNIP--]
> diff --git a/package/python-pydantic-core/python-pydantic-core.mk b/package/python-pydantic-core/python-pydantic-core.mk
> new file mode 100644
> index 0000000000..8b61323ab3
> --- /dev/null
> +++ b/package/python-pydantic-core/python-pydantic-core.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# python-pydantic-core
> +#
> +################################################################################
> +
> +PYTHON_PYDANTIC_CORE_VERSION = 2.14.5
> +PYTHON_PYDANTIC_CORE_SOURCE = pydantic_core-$(PYTHON_PYDANTIC_CORE_VERSION).tar.gz
> +PYTHON_PYDANTIC_CORE_SITE = https://files.pythonhosted.org/packages/64/26/cffb93fe9c6b5a91c497f37fae14a4b073ecbc47fc36a9979c7aa888b245
> +PYTHON_PYDANTIC_CORE_SETUP_TYPE = maturin
> +PYTHON_PYDANTIC_CORE_LICENSE = MIT
> +PYTHON_PYDANTIC_CORE_LICENSE_FILES = LICENSE
> +PYTHON_PYDANTIC_CORE_DEPENDENCIES = host-python-typing-extensions

[0] ... why there was dependency on the rust toolchain.

So I looked at the manual [1] to check the maturin setup type, but... It
is *not* documented (although I seem to remember I already asked that it
be, I can't find that mail, so let's say this is the first time I bring
up the subject...)

So I had to look at the code, and see that the rust toolchain is
automatically added when the setup type is maturin.

As I had no idea that maturin was explicitly about python-packages-
written-in-rust, the dependency on rust was not obvious to me... :-/

Could you please extend the manual to descrbe the additional setup types
that are currently supported by Buildroot, please?

[1] https://buildroot.org/downloads/manual/manual.html#_infrastructure_for_python_packages

Regards,
Yann E. MORIN.

> +
> +$(eval $(python-package))
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: new package

[James Hilliard]

On Sat, Nov 25, 2023 at 8:36 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>
> James, All,
>
> On 2023-11-25 01:10 -0700, James Hilliard spake thusly:
> > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> > ---
> >  package/Config.in                                 |  1 +
> >  package/python-pydantic-core/Config.in            |  8 ++++++++
> >  .../python-pydantic-core.hash                     |  4 ++++
> >  .../python-pydantic-core/python-pydantic-core.mk  | 15 +++++++++++++++
> >  4 files changed, 28 insertions(+)
> >  create mode 100644 package/python-pydantic-core/Config.in
> >  create mode 100644 package/python-pydantic-core/python-pydantic-core.hash
> >  create mode 100644 package/python-pydantic-core/python-pydantic-core.mk
> >
> > diff --git a/package/Config.in b/package/Config.in
> > index 68e6e29a4d..fcc09b07c4 100644
> > --- a/package/Config.in
> > +++ b/package/Config.in
> > @@ -1228,6 +1228,7 @@ menu "External python modules"
> >       source "package/python-pycups/Config.in"
> >       source "package/python-pydal/Config.in"
> >       source "package/python-pydantic/Config.in"
> > +     source "package/python-pydantic-core/Config.in"
> >       source "package/python-pydevmem/Config.in"
> >       source "package/python-pydyf/Config.in"
> >       source "package/python-pyelftools/Config.in"
> > diff --git a/package/python-pydantic-core/Config.in b/package/python-pydantic-core/Config.in
> > new file mode 100644
> > index 0000000000..3eeb1844a2
> > --- /dev/null
> > +++ b/package/python-pydantic-core/Config.in
> > @@ -0,0 +1,8 @@
> > +config BR2_PACKAGE_PYTHON_PYDANTIC_CORE
> > +     bool "python-pydantic-core"
> > +     depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
> > +     select BR2_PACKAGE_PYTHON_TYPING_EXTENSIONS # runtime
> > +     help
>
> So what happens if I apply this patch, which adds pydantic-core, but I
> do not apply the next one, which bumps pydantic, so we end up in a
> situation with an old pydantic, with the new core also installed?
>
> Do the two conflict, or is it an OK situation (obviously the
> pydantic-core would be of little use)?

It's OK.

>
> If there is a conflict, then we will want to introduce the new package
> at the same time we do the bump, and that should be explained int he
> commit log.
>
> If there is no conflict, then just say, we can ammend the commit log
> accordignly.

There's no conflict since pydantic-core is a new package with no reverse
dependencies.

>
>
> > +       Core validation logic for pydantic written in rust.
>
> As it is written in rust, I was wondering... [0]
>
> [--SNIP--]
> > diff --git a/package/python-pydantic-core/python-pydantic-core.mk b/package/python-pydantic-core/python-pydantic-core.mk
> > new file mode 100644
> > index 0000000000..8b61323ab3
> > --- /dev/null
> > +++ b/package/python-pydantic-core/python-pydantic-core.mk
> > @@ -0,0 +1,15 @@
> > +################################################################################
> > +#
> > +# python-pydantic-core
> > +#
> > +################################################################################
> > +
> > +PYTHON_PYDANTIC_CORE_VERSION = 2.14.5
> > +PYTHON_PYDANTIC_CORE_SOURCE = pydantic_core-$(PYTHON_PYDANTIC_CORE_VERSION).tar.gz
> > +PYTHON_PYDANTIC_CORE_SITE = https://files.pythonhosted.org/packages/64/26/cffb93fe9c6b5a91c497f37fae14a4b073ecbc47fc36a9979c7aa888b245
> > +PYTHON_PYDANTIC_CORE_SETUP_TYPE = maturin
> > +PYTHON_PYDANTIC_CORE_LICENSE = MIT
> > +PYTHON_PYDANTIC_CORE_LICENSE_FILES = LICENSE
> > +PYTHON_PYDANTIC_CORE_DEPENDENCIES = host-python-typing-extensions
>
> [0] ... why there was dependency on the rust toolchain.
>
> So I looked at the manual [1] to check the maturin setup type, but... It
> is *not* documented (although I seem to remember I already asked that it
> be, I can't find that mail, so let's say this is the first time I bring
> up the subject...)
>
> So I had to look at the code, and see that the rust toolchain is
> automatically added when the setup type is maturin.
>
> As I had no idea that maturin was explicitly about python-packages-
> written-in-rust, the dependency on rust was not obvious to me... :-/
>
> Could you please extend the manual to descrbe the additional setup types
> that are currently supported by Buildroot, please?

Yeah, so we're pretty close right now to having all our python infrastructure
migrated to pep517 so I was thinking once we have that then a lot of things
including the documentation can be significantly simplified as maturin and
setuptools-rust infrastructure will be pep517 based and we can drop all the
legacy docs like distutils and the docs related to legacy non-pep517 setuptools.

>
> [1] https://buildroot.org/downloads/manual/manual.html#_infrastructure_for_python_packages
>
> Regards,
> Yann E. MORIN.
>
> > +
> > +$(eval $(python-package))
> > --
> > 2.34.1
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
>
> --
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> | +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> '------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: new package

[Yann E. MORIN]

James, All,

On 2023-11-25 17:11 -0700, James Hilliard spake thusly:
> On Sat, Nov 25, 2023 at 8:36 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
[--SNIP--]
> > So what happens if I apply this patch, which adds pydantic-core, but I
> > do not apply the next one, which bumps pydantic, so we end up in a
> > situation with an old pydantic, with the new core also installed?
> >
> > Do the two conflict, or is it an OK situation (obviously the
> > pydantic-core would be of little use)?
> >
> > If there is a conflict, then we will want to introduce the new package
> > at the same time we do the bump, and that should be explained int he
> > commit log.
> >
> > If there is no conflict, then just say, we can ammend the commit log
> > accordignly.
> 
> There's no conflict since pydantic-core is a new package with no reverse
> dependencies.

It is not just about reverse dependencies. Assuming we just apply the
pydantic-core new package, and keep the old pydantic (e.g we have to
revert the bump later for various reasons), what happens at build time
or at runtime, if the user enables pydantic-core and pydantic (the old)?

If that makes pydantic-old fail to build or run, that is what we care
about.

[--SNIP--]
> > Could you please extend the manual to descrbe the additional setup types
> > that are currently supported by Buildroot, please?
> Yeah, so we're pretty close right now to having all our python infrastructure
> migrated to pep517 so I was thinking once we have that then a lot of things
> including the documentation can be significantly simplified as maturin and
> setuptools-rust infrastructure will be pep517 based and we can drop all the
> legacy docs like distutils and the docs related to legacy non-pep517 setuptools.

But none of that is on master, for the release to come, so we would stil
need the manual to be up-to-date for master.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: new package

[James Hilliard]

On Sun, Nov 26, 2023 at 4:27 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>
> James, All,
>
> On 2023-11-25 17:11 -0700, James Hilliard spake thusly:
> > On Sat, Nov 25, 2023 at 8:36 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> [--SNIP--]
> > > So what happens if I apply this patch, which adds pydantic-core, but I
> > > do not apply the next one, which bumps pydantic, so we end up in a
> > > situation with an old pydantic, with the new core also installed?
> > >
> > > Do the two conflict, or is it an OK situation (obviously the
> > > pydantic-core would be of little use)?
> > >
> > > If there is a conflict, then we will want to introduce the new package
> > > at the same time we do the bump, and that should be explained int he
> > > commit log.
> > >
> > > If there is no conflict, then just say, we can ammend the commit log
> > > accordignly.
> >
> > There's no conflict since pydantic-core is a new package with no reverse
> > dependencies.
>
> It is not just about reverse dependencies. Assuming we just apply the
> pydantic-core new package, and keep the old pydantic (e.g we have to
> revert the bump later for various reasons), what happens at build time
> or at runtime, if the user enables pydantic-core and pydantic (the old)?

So pydantic-core is just a new dependency for pydantic to handle core
validation logic. If pydantic-core is used with old pydantic there shouldn't
be any build/runtime issues as they would not conflict in any way.

>
> If that makes pydantic-old fail to build or run, that is what we care
> about.

Why would it make pydantic-old fail? The pydantic-core package uses a
different module namespace which is typically how python packages
prevent import conflicts in general.

To import from pydantic-core you import like:
from pydantic_core import SchemaValidator, ValidationError

To import from pydantic you import like:
from pydantic import BaseModel

New pydantic simply internally imports from pydantic_core but old
pydantic does not and will function the same whether or not we have
pydantic_core installed.



>
> [--SNIP--]
> > > Could you please extend the manual to descrbe the additional setup types
> > > that are currently supported by Buildroot, please?
> > Yeah, so we're pretty close right now to having all our python infrastructure
> > migrated to pep517 so I was thinking once we have that then a lot of things
> > including the documentation can be significantly simplified as maturin and
> > setuptools-rust infrastructure will be pep517 based and we can drop all the
> > legacy docs like distutils and the docs related to legacy non-pep517 setuptools.
>
> But none of that is on master, for the release to come, so we would stil
> need the manual to be up-to-date for master.
>
> Regards,
> Yann E. MORIN.
>
> --
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> | +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> '------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: new package

[Yann E. MORIN]

James, All,

On 2023-11-26 09:19 -0700, James Hilliard spake thusly:
> On Sun, Nov 26, 2023 at 4:27 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > > On Sat, Nov 25, 2023 at 8:36 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
[--SNIP--]
> > > There's no conflict since pydantic-core is a new package with no reverse
> > > dependencies.
> > It is not just about reverse dependencies. Assuming we just apply the
> > pydantic-core new package, and keep the old pydantic (e.g we have to
> > revert the bump later for various reasons), what happens at build time
> > or at runtime, if the user enables pydantic-core and pydantic (the old)?
> So pydantic-core is just a new dependency for pydantic to handle core
> validation logic. If pydantic-core is used with old pydantic there shouldn't
> be any build/runtime issues as they would not conflict in any way.
> 
> > If that makes pydantic-old fail to build or run, that is what we care
> > about.
> Why would it make pydantic-old fail? The pydantic-core package uses a
> different module namespace which is typically how python packages
> prevent import conflicts in general.
> 
> To import from pydantic-core you import like:
> from pydantic_core import SchemaValidator, ValidationError
> 
> To import from pydantic you import like:
> from pydantic import BaseModel
> 
> New pydantic simply internally imports from pydantic_core but old
> pydantic does not and will function the same whether or not we have
> pydantic_core installed.

So, pydantic-core does not provide a subset of the modules previously in
pydantic, so there will not be a conflict.

Thanks for the explanations. :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: new package

[James Hilliard]

On Sun, Nov 26, 2023 at 9:40 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>
> James, All,
>
> On 2023-11-26 09:19 -0700, James Hilliard spake thusly:
> > On Sun, Nov 26, 2023 at 4:27 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > > > On Sat, Nov 25, 2023 at 8:36 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> [--SNIP--]
> > > > There's no conflict since pydantic-core is a new package with no reverse
> > > > dependencies.
> > > It is not just about reverse dependencies. Assuming we just apply the
> > > pydantic-core new package, and keep the old pydantic (e.g we have to
> > > revert the bump later for various reasons), what happens at build time
> > > or at runtime, if the user enables pydantic-core and pydantic (the old)?
> > So pydantic-core is just a new dependency for pydantic to handle core
> > validation logic. If pydantic-core is used with old pydantic there shouldn't
> > be any build/runtime issues as they would not conflict in any way.
> >
> > > If that makes pydantic-old fail to build or run, that is what we care
> > > about.
> > Why would it make pydantic-old fail? The pydantic-core package uses a
> > different module namespace which is typically how python packages
> > prevent import conflicts in general.
> >
> > To import from pydantic-core you import like:
> > from pydantic_core import SchemaValidator, ValidationError
> >
> > To import from pydantic you import like:
> > from pydantic import BaseModel
> >
> > New pydantic simply internally imports from pydantic_core but old
> > pydantic does not and will function the same whether or not we have
> > pydantic_core installed.
>
> So, pydantic-core does not provide a subset of the modules previously in
> pydantic, so there will not be a conflict.

Well to clarify pydantic-core likely implements a subset of the functionality in
old-pydantic, however by using a different module namespace there is no
conflict.


>
> Thanks for the explanations. :-)
>
> Regards,
> Yann E. MORIN.
>
> --
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> | +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> '------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: new package

[Yann E. MORIN]

James, All,

On 2023-11-25 01:10 -0700, James Hilliard spake thusly:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

Applied to next, after exapnding the commit log with a summary of your
explanations, thanks!

Regards,
Yann E. MORIN.

> ---
>  package/Config.in                                 |  1 +
>  package/python-pydantic-core/Config.in            |  8 ++++++++
>  .../python-pydantic-core.hash                     |  4 ++++
>  .../python-pydantic-core/python-pydantic-core.mk  | 15 +++++++++++++++
>  4 files changed, 28 insertions(+)
>  create mode 100644 package/python-pydantic-core/Config.in
>  create mode 100644 package/python-pydantic-core/python-pydantic-core.hash
>  create mode 100644 package/python-pydantic-core/python-pydantic-core.mk
> 
> diff --git a/package/Config.in b/package/Config.in
> index 68e6e29a4d..fcc09b07c4 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -1228,6 +1228,7 @@ menu "External python modules"
>  	source "package/python-pycups/Config.in"
>  	source "package/python-pydal/Config.in"
>  	source "package/python-pydantic/Config.in"
> +	source "package/python-pydantic-core/Config.in"
>  	source "package/python-pydevmem/Config.in"
>  	source "package/python-pydyf/Config.in"
>  	source "package/python-pyelftools/Config.in"
> diff --git a/package/python-pydantic-core/Config.in b/package/python-pydantic-core/Config.in
> new file mode 100644
> index 0000000000..3eeb1844a2
> --- /dev/null
> +++ b/package/python-pydantic-core/Config.in
> @@ -0,0 +1,8 @@
> +config BR2_PACKAGE_PYTHON_PYDANTIC_CORE
> +	bool "python-pydantic-core"
> +	depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
> +	select BR2_PACKAGE_PYTHON_TYPING_EXTENSIONS # runtime
> +	help
> +	  Core validation logic for pydantic written in rust.
> +
> +	  https://github.com/pydantic/pydantic-core
> diff --git a/package/python-pydantic-core/python-pydantic-core.hash b/package/python-pydantic-core/python-pydantic-core.hash
> new file mode 100644
> index 0000000000..4927d816be
> --- /dev/null
> +++ b/package/python-pydantic-core/python-pydantic-core.hash
> @@ -0,0 +1,4 @@
> +# Locally calculated after vendoring
> +sha256  b54296f8317e7ffd72726836636aa3a6c8c977d8f73b68253c443c0fe3731064  pydantic_core-2.14.5.tar.gz
> +# Locally computed sha256 checksums
> +sha256  2afdd30d54b4d62b6f488a6bcc1546e84ec5061f13f4209c03d012348783795a  LICENSE
> diff --git a/package/python-pydantic-core/python-pydantic-core.mk b/package/python-pydantic-core/python-pydantic-core.mk
> new file mode 100644
> index 0000000000..8b61323ab3
> --- /dev/null
> +++ b/package/python-pydantic-core/python-pydantic-core.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# python-pydantic-core
> +#
> +################################################################################
> +
> +PYTHON_PYDANTIC_CORE_VERSION = 2.14.5
> +PYTHON_PYDANTIC_CORE_SOURCE = pydantic_core-$(PYTHON_PYDANTIC_CORE_VERSION).tar.gz
> +PYTHON_PYDANTIC_CORE_SITE = https://files.pythonhosted.org/packages/64/26/cffb93fe9c6b5a91c497f37fae14a4b073ecbc47fc36a9979c7aa888b245
> +PYTHON_PYDANTIC_CORE_SETUP_TYPE = maturin
> +PYTHON_PYDANTIC_CORE_LICENSE = MIT
> +PYTHON_PYDANTIC_CORE_LICENSE_FILES = LICENSE
> +PYTHON_PYDANTIC_CORE_DEPENDENCIES = host-python-typing-extensions
> +
> +$(eval $(python-package))
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

[Buildroot] [PATCH 3/3] package/python-pydantic: bump to version 2.5.2

[James Hilliard]

Add new python-annotated-types runtime dependency.

Add new python-pydantic-core runtime dependency.

Migrate build backend from setuptools to hatchling.

License hash changed due to adding contributors:
https://github.com/pydantic/pydantic/commit/7bc9c6525a81680c0dd9df3558ed5f33345a77c2

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
 package/python-pydantic/Config.in            | 5 ++++-
 package/python-pydantic/python-pydantic.hash | 6 +++---
 package/python-pydantic/python-pydantic.mk   | 9 ++++++---
 3 files changed, 13 insertions(+), 7 deletions(-)

diff --git a/package/python-pydantic/Config.in b/package/python-pydantic/Config.in
index 41ec43adf4..e9cd2e6780 100644
--- a/package/python-pydantic/Config.in
+++ b/package/python-pydantic/Config.in
@@ -1,8 +1,11 @@
 config BR2_PACKAGE_PYTHON_PYDANTIC
 	bool "python-pydantic"
+	depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS # python-pydantic-core
+	select BR2_PACKAGE_PYTHON_ANNOTATED_TYPES # runtime
+	select BR2_PACKAGE_PYTHON_PYDANTIC_CORE # runtime
 	select BR2_PACKAGE_PYTHON_TYPING_EXTENSIONS # runtime
 	help
 	  Data validation and settings management using python 3.6
 	  type hinting.
 
-	  https://github.com/samuelcolvin/pydantic
+	  https://github.com/pydantic/pydantic
diff --git a/package/python-pydantic/python-pydantic.hash b/package/python-pydantic/python-pydantic.hash
index 88b17f4575..0848debc1c 100644
--- a/package/python-pydantic/python-pydantic.hash
+++ b/package/python-pydantic/python-pydantic.hash
@@ -1,5 +1,5 @@
 # md5, sha256 from https://pypi.org/pypi/pydantic/json
-md5  f0e286c32f40ec45aba9603742739cd6  pydantic-1.10.8.tar.gz
-sha256  1410275520dfa70effadf4c21811d755e7ef9bb1f1d077a21958153a92c8d9ca  pydantic-1.10.8.tar.gz
+md5  348281a5a27eb5253c7a83927aae64e1  pydantic-2.5.2.tar.gz
+sha256  ff177ba64c6faf73d7afa2e8cad38fd456c0dbe01c9954e71038001cd15a6edd  pydantic-2.5.2.tar.gz
 # Locally computed sha256 checksums
-sha256  9e3946690ac88b6b73e8f001a0586af13568be8852fd514e4393f39761764387  LICENSE
+sha256  a9e186f3ca16b5eef84318e7a701721351a00cb7b8ae3a4394b67b49e3529ef3  LICENSE
diff --git a/package/python-pydantic/python-pydantic.mk b/package/python-pydantic/python-pydantic.mk
index b800426d22..b5bb7ff853 100644
--- a/package/python-pydantic/python-pydantic.mk
+++ b/package/python-pydantic/python-pydantic.mk
@@ -4,11 +4,14 @@
 #
 ################################################################################
 
-PYTHON_PYDANTIC_VERSION = 1.10.8
+PYTHON_PYDANTIC_VERSION = 2.5.2
 PYTHON_PYDANTIC_SOURCE = pydantic-$(PYTHON_PYDANTIC_VERSION).tar.gz
-PYTHON_PYDANTIC_SITE = https://files.pythonhosted.org/packages/23/65/2aa13873e9e0084ecaec00fbe6c6096b65e1ab99ba66bdbf7e4e7c4cc915
-PYTHON_PYDANTIC_SETUP_TYPE = setuptools
+PYTHON_PYDANTIC_SITE = https://files.pythonhosted.org/packages/b7/41/3c8108f79fb7da2d2b17f35744232af4ffcd9e764ebe1e3fd4b26669b325
+PYTHON_PYDANTIC_SETUP_TYPE = pep517
 PYTHON_PYDANTIC_LICENSE = MIT
 PYTHON_PYDANTIC_LICENSE_FILES = LICENSE
+PYTHON_PYDANTIC_DEPENDENCIES = \
+	host-python-hatchling \
+	host-python-hatch-fancy-pypi-readme
 
 $(eval $(python-package))
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 3/3] package/python-pydantic: bump to version 2.5.2

[Yann E. MORIN]

James, All,

On 2023-11-25 01:10 -0700, James Hilliard spake thusly:
> Add new python-annotated-types runtime dependency.
> 
> Add new python-pydantic-core runtime dependency.
> 
> Migrate build backend from setuptools to hatchling.
> 
> License hash changed due to adding contributors:
> https://github.com/pydantic/pydantic/commit/7bc9c6525a81680c0dd9df3558ed5f33345a77c2
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

Applied to next, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/python-pydantic/Config.in            | 5 ++++-
>  package/python-pydantic/python-pydantic.hash | 6 +++---
>  package/python-pydantic/python-pydantic.mk   | 9 ++++++---
>  3 files changed, 13 insertions(+), 7 deletions(-)
> 
> diff --git a/package/python-pydantic/Config.in b/package/python-pydantic/Config.in
> index 41ec43adf4..e9cd2e6780 100644
> --- a/package/python-pydantic/Config.in
> +++ b/package/python-pydantic/Config.in
> @@ -1,8 +1,11 @@
>  config BR2_PACKAGE_PYTHON_PYDANTIC
>  	bool "python-pydantic"
> +	depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS # python-pydantic-core
> +	select BR2_PACKAGE_PYTHON_ANNOTATED_TYPES # runtime
> +	select BR2_PACKAGE_PYTHON_PYDANTIC_CORE # runtime
>  	select BR2_PACKAGE_PYTHON_TYPING_EXTENSIONS # runtime
>  	help
>  	  Data validation and settings management using python 3.6
>  	  type hinting.
>  
> -	  https://github.com/samuelcolvin/pydantic
> +	  https://github.com/pydantic/pydantic
> diff --git a/package/python-pydantic/python-pydantic.hash b/package/python-pydantic/python-pydantic.hash
> index 88b17f4575..0848debc1c 100644
> --- a/package/python-pydantic/python-pydantic.hash
> +++ b/package/python-pydantic/python-pydantic.hash
> @@ -1,5 +1,5 @@
>  # md5, sha256 from https://pypi.org/pypi/pydantic/json
> -md5  f0e286c32f40ec45aba9603742739cd6  pydantic-1.10.8.tar.gz
> -sha256  1410275520dfa70effadf4c21811d755e7ef9bb1f1d077a21958153a92c8d9ca  pydantic-1.10.8.tar.gz
> +md5  348281a5a27eb5253c7a83927aae64e1  pydantic-2.5.2.tar.gz
> +sha256  ff177ba64c6faf73d7afa2e8cad38fd456c0dbe01c9954e71038001cd15a6edd  pydantic-2.5.2.tar.gz
>  # Locally computed sha256 checksums
> -sha256  9e3946690ac88b6b73e8f001a0586af13568be8852fd514e4393f39761764387  LICENSE
> +sha256  a9e186f3ca16b5eef84318e7a701721351a00cb7b8ae3a4394b67b49e3529ef3  LICENSE
> diff --git a/package/python-pydantic/python-pydantic.mk b/package/python-pydantic/python-pydantic.mk
> index b800426d22..b5bb7ff853 100644
> --- a/package/python-pydantic/python-pydantic.mk
> +++ b/package/python-pydantic/python-pydantic.mk
> @@ -4,11 +4,14 @@
>  #
>  ################################################################################
>  
> -PYTHON_PYDANTIC_VERSION = 1.10.8
> +PYTHON_PYDANTIC_VERSION = 2.5.2
>  PYTHON_PYDANTIC_SOURCE = pydantic-$(PYTHON_PYDANTIC_VERSION).tar.gz
> -PYTHON_PYDANTIC_SITE = https://files.pythonhosted.org/packages/23/65/2aa13873e9e0084ecaec00fbe6c6096b65e1ab99ba66bdbf7e4e7c4cc915
> -PYTHON_PYDANTIC_SETUP_TYPE = setuptools
> +PYTHON_PYDANTIC_SITE = https://files.pythonhosted.org/packages/b7/41/3c8108f79fb7da2d2b17f35744232af4ffcd9e764ebe1e3fd4b26669b325
> +PYTHON_PYDANTIC_SETUP_TYPE = pep517
>  PYTHON_PYDANTIC_LICENSE = MIT
>  PYTHON_PYDANTIC_LICENSE_FILES = LICENSE
> +PYTHON_PYDANTIC_DEPENDENCIES = \
> +	host-python-hatchling \
> +	host-python-hatch-fancy-pypi-readme
>  
>  $(eval $(python-package))
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/3] package/python-annotated-types: new package

[Yann E. MORIN]

James, All,

On 2023-11-25 01:10 -0700, James Hilliard spake thusly:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

Applied to next, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/Config.in                                 |  1 +
>  package/python-annotated-types/Config.in          |  6 ++++++
>  .../python-annotated-types.hash                   |  5 +++++
>  .../python-annotated-types.mk                     | 15 +++++++++++++++
>  4 files changed, 27 insertions(+)
>  create mode 100644 package/python-annotated-types/Config.in
>  create mode 100644 package/python-annotated-types/python-annotated-types.hash
>  create mode 100644 package/python-annotated-types/python-annotated-types.mk
> 
> diff --git a/package/Config.in b/package/Config.in
> index 5a3410d758..68e6e29a4d 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -974,6 +974,7 @@ menu "External python modules"
>  	source "package/python-aiozipkin/Config.in"
>  	source "package/python-alembic/Config.in"
>  	source "package/python-alsaaudio/Config.in"
> +	source "package/python-annotated-types/Config.in"
>  	source "package/python-ansicolors/Config.in"
>  	source "package/python-apispec/Config.in"
>  	source "package/python-appdirs/Config.in"
> diff --git a/package/python-annotated-types/Config.in b/package/python-annotated-types/Config.in
> new file mode 100644
> index 0000000000..36525a526b
> --- /dev/null
> +++ b/package/python-annotated-types/Config.in
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_PYTHON_ANNOTATED_TYPES
> +	bool "python-annotated-types"
> +	help
> +	  Reusable constraint types to use with typing.Annotated.
> +
> +	  https://github.com/annotated-types/annotated-types
> diff --git a/package/python-annotated-types/python-annotated-types.hash b/package/python-annotated-types/python-annotated-types.hash
> new file mode 100644
> index 0000000000..1663bcb51f
> --- /dev/null
> +++ b/package/python-annotated-types/python-annotated-types.hash
> @@ -0,0 +1,5 @@
> +# md5, sha256 from https://pypi.org/pypi/annotated-types/json
> +md5  5fe2125b08851f0d05a8efad6456861c  annotated_types-0.6.0.tar.gz
> +sha256  563339e807e53ffd9c267e99fc6d9ea23eb8443c08f112651963e24e22f84a5d  annotated_types-0.6.0.tar.gz
> +# Locally computed sha256 checksums
> +sha256  fe1049884b1a0d9342901e88e07f32925d24b3121d9972b6a6805fb9824b095d  LICENSE
> diff --git a/package/python-annotated-types/python-annotated-types.mk b/package/python-annotated-types/python-annotated-types.mk
> new file mode 100644
> index 0000000000..8bc617069d
> --- /dev/null
> +++ b/package/python-annotated-types/python-annotated-types.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# python-annotated-types
> +#
> +################################################################################
> +
> +PYTHON_ANNOTATED_TYPES_VERSION = 0.6.0
> +PYTHON_ANNOTATED_TYPES_SOURCE = annotated_types-$(PYTHON_ANNOTATED_TYPES_VERSION).tar.gz
> +PYTHON_ANNOTATED_TYPES_SITE = https://files.pythonhosted.org/packages/67/fe/8c7b275824c6d2cd17c93ee85d0ee81c090285b6d52f4876ccc47cf9c3c4
> +PYTHON_ANNOTATED_TYPES_SETUP_TYPE = pep517
> +PYTHON_ANNOTATED_TYPES_LICENSE = MIT
> +PYTHON_ANNOTATED_TYPES_LICENSE_FILES = LICENSE
> +PYTHON_ANNOTATED_TYPES_DEPENDENCIES = host-python-hatchling
> +
> +$(eval $(python-package))
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot