On Thu, Oct 23, 2025 at 07:50:36PM +0100, Heinrich Schuchardt wrote: > Am 23. Oktober 2025 18:40:59 GMT+01:00 schrieb Tom Rini <[email protected]>: > >A frequently reported problem is that someone misses a required python > >package when doing a specific task within U-Boot. This is in turn > >because each of our requirements.txt files only lists their direct > >dependencies. It is not always clear that another tool has its own > >requirements and thus something else fails. Solve this by having a top > >level requirements.txt file for the project which in turn installs all > >of our other project requirements.txt files. > > > >Signed-off-by: Tom Rini <[email protected]> > >--- > >Cc: Heinrich Schuchardt <[email protected]> > >Cc: Simon Glass <[email protected]> > >Cc: Kory Maincent <[email protected]> > > > >As Kory is the most recent person to hit this, cc'ing them. I think this > >is the right path forward and if agreed, I'll update documentation in a > >follow-up. > >--- > > requirements.txt | 8 ++++++++ > > 1 file changed, 8 insertions(+) > > create mode 100644 requirements.txt > > > >diff --git a/requirements.txt b/requirements.txt > >new file mode 100644 > >index 000000000000..0fd08b9da17b > >--- /dev/null > >+++ b/requirements.txt > >@@ -0,0 +1,8 @@ > >+# For ease of use, this is all requirements files for all portions > >+# of U-Boot > >+-r doc/sphinx/requirements.txt > >+-r tools/u_boot_pylib/requirements.txt > >+-r tools/buildman/requirements.txt > >+-r tools/binman/requirements.txt > >+-r tools/patman/requirements.txt > >+-r test/py/requirements.txt > > These individual files may require different versions of the same package.
They may not, that would break creating our containers for CI. > Either the individual files should be feature complete for each CI > step, or we should move to a single requirements file. This would be even further against python best practices than we already have been. -- Tom
signature.asc
Description: PGP signature
