[PATCH 0/6] Rework requirements.txt files
Tom Rini
trini at konsulko.com
Sat Feb 15 22:28:54 CET 2025
On Tue, 04 Feb 2025 17:12:03 -0600, Tom Rini wrote:
> Hey all,
>
> A challenge we've run in to is making it easier for more people to use
> various python tools that we include in the tree. Part of the problem is
> that when we have a requirements.txt file, aside from the doc one we
> share with the kernel, I created it using "pip freeze". And while this
> might have been a best (or at least OK) practice at the time, that's no
> longer the case and is why our files have so many things in them. What
> this series does is create multiple files, one per project/tool and then
> has CI install them as needed. There's a few places here where this
> means that we update the requirements as well, but we keep a few big
> things where they are currently. This is because updating them
> introduces problems of their own and delaing with that would best be a
> follow up series. I've put this through GitLab and Azure to make sure
> everything is still going fine on both platforms.
>
> [...]
Applied to u-boot/next, thanks!
--
Tom
More information about the U-Boot
mailing list