From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Abilio Marques <abiliojr@gmail.com>
Cc: Chris Packham <judge.packham@gmail.com>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/micropython: make use of recent micropython-lib
Date: Sun, 28 Jan 2024 22:02:44 +0100 [thread overview]
Message-ID: <ZbbA9L77KcWxTr_y@landeda> (raw)
In-Reply-To: <CAEWqYrWrwGjAsNht+0bjJyXaTc3XGwpz+cdZGoQHCrzifYSYMQ@mail.gmail.com>
Abilio, All,
On 2024-01-28 11:28 -0800, Abilio Marques spake thusly:
> Because this is my first buildroot submission, I tried to keep it simple. It
> makes use of existing micropython tools (used to process manifests) to discover
> the list of packages available in micropython-lib. My hope is that by relying
> on them, any future changes in directory structure will be covered by their own
> "manifestfile.py" tool.
This is a good rationale, and maybe you can add that to the commit log.
> Also, it still copies the files as plain source code ".py" files. I did it this
> way to avoid abrupt changes that could annoy people using the package.
Yes, agreed.
> I have an idea that mixes part of my code (the one that discovers the packages)
> and freezes them (using the same manifests tool), but I thought it would be a
> bridge too far for a successful first submission.
Agreed: I like that your commit does not change the existing behaviour.
This is good.
> Also, I want to find time to
> make it configurable using menuconfig options (each one has it's drawbacks):
> - frozen as mpy files
> - frozen inside the micropython binary
> - keep current text files
We have a similar choice for the full-blown CPython, where we can keep
only .py files, keep only .pyc files, or keep both. So si=uch a choice
for micropython seems totally acceptable. Just o make your future
changes better, it would be two separate changes;
1. introduce frozen vs. text choice
2. add frozen-in-binary to the choice
> If there is interest, I can prepare it in a couple weeks from now. Ideas are
> welcomed.
The interest is on your side: if you do not have that interest, do not
do it just for the show; a new feature needs to have someone that
actually needs it and tested it (to some extent).
And speaking of tests, we now have a micropython test:
support/testing/tests/package/test_micropython.py
So it would be nice that, when/if you add the frozen support, you extend
that test to also test frozen libs.
Thanks!
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
next prev parent reply other threads:[~2024-01-28 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240128183024.3322187-1-abiliojr@gmail.com>
2024-01-28 18:58 ` [Buildroot] [PATCH] package/micropython: make use of recent micropython-lib Chris Packham
2024-01-28 19:28 ` Abilio Marques
2024-01-28 21:02 ` Yann E. MORIN [this message]
2024-01-28 20:09 ` Yann E. MORIN
2024-01-28 20:56 ` Abilio Marques
2024-01-28 21:22 ` Yann E. MORIN
2024-01-28 18:37 Abilio Marques
2024-01-28 20:03 ` Yann E. MORIN
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=ZbbA9L77KcWxTr_y@landeda \
--to=yann.morin.1998@free.fr \
--cc=abiliojr@gmail.com \
--cc=buildroot@buildroot.org \
--cc=judge.packham@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.