As a rule of thumb, any project involving a substantial amount of Python
always ends up needing a Docker container to build. So I'm in the "no" camp
for making Python a dependency, however I think it's fine to keep things
as-is where it can be used for helper scripts and utilities for specific
Thanks for bringing this to the list, Patrick.
Stefan Reinauer wrote:
> Given the mess that Python 2 to Python 3 conversion has been (and
> still is), this is just inviting a lot of trouble into what has
> been a fairly stable part of coreboot for the last decade.
I strongly agree.
On a more
> What coreboot problems that we have seen in the past are we actually
solving with these rewrites?
To be a bit more blunt, what is expected to be improved by writing it in
python?
Utilities, eg. to analyse blobs?
Menu and configuration of builds?
Packing blobs for flashing?
I could see some
Thanks Patrick for bringing this in.
Regarding Pytest for utils (https://review.coreboot.org/c/coreboot/+/57869
), what's the recommended way to test the tools that are placed in "util/*"
?
I noticed that most of them don't have any kind of end-to-end test (I
couldn't find a single one, but
Since it didn't look like I would be able to get coreboot working on
this laptop, I returned it. I still have all the hardware info I
collected. Is this useful to anyone?
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to
On Wed, Sep 29, 2021 at 7:44 AM Jack Rosenthal wrote:
> Overall I think introducing Python to the build would provide net benefit,
> mainly from Kconfiglib, but could also find other good uses in e2e tests
> like Ricardo was working on. Most people's Linux distros ship with a Python
>
Am Mi., 29. Sept. 2021 um 19:47 Uhr schrieb Jack Rosenthal <
jrose...@google.com>:
> At a minimum, I think we should consider introducing Python on an optional
>>> basis (i.e., the C Kconfig implementation only gets used if a Python
>>> interpreter is unavailable), but making it required would be
On Wed, Sep 29, 2021 at 9:57 AM Patrick Georgi wrote:
> Am Mi., 29. Sept. 2021 um 16:43 Uhr schrieb Jack Rosenthal <
> jrose...@google.com>:
>
>> Overall I think introducing Python to the build would provide net
>> benefit, mainly from Kconfiglib, but could also find other good uses in e2e
>>
Overall I think introducing Python to the build would provide net benefit,
mainly from Kconfiglib, but could also find other good uses in e2e tests
like Ricardo was working on. Most people's Linux distros ship with a Python
interpreter too, so most developers would be unlikely to notice the extra
Am Mi., 29. Sept. 2021 um 16:43 Uhr schrieb Jack Rosenthal <
jrose...@google.com>:
> Overall I think introducing Python to the build would provide net benefit,
> mainly from Kconfiglib, but could also find other good uses in e2e tests
> like Ricardo was working on. Most people's Linux distros
Hi Patrick,
That's good to hear, would there be change to "make menuconfig" with
kconfiglib
Thanks
Ranga
On Wed, Sep 29, 2021 at 10:58 AM Patrick Georgi via coreboot <
coreboot@coreboot.org> wrote:
> Hi everybody,
>
> Historically, coreboot avoided depending on python too much (we got rid of
>
Hi everybody,
Historically, coreboot avoided depending on python too much (we got rid of
an entire python based configuration and build system, for example), with
few minor exceptions.
The main reason has been that while python code is quick to slap together,
it has demonstrated a penchant for
12 matches
Mail list logo
