On Fri, Jan 23, 2026 at 11:11 AM Bruce Richardson <[email protected]> wrote: . > > > > Okay, both of the options above sound good. From my end if I had to > > choose I would just do the first solution (install meson at runtime in > > all cases) because it keeps our process uniform across distro testing > > and there is no "special" container. But, the second option sounds good > > too so please let me know what you think is best. > > > > Go with your runtime solution, it's fine - and possibly better.
I realized after looking at our scripting that I pushed a change last year that does the "meet meson version at runtime based on the output of buildtools/get-min-meson-version.py" last year. That was probably when you originally added buildtools/get-min-meson-version.py. So, I guess we can say that no coordination with the UNH group is needed when the meson version is bumped in the future. The same should be true for the other labs because as far as I know they are using dpdk/.ci/linux-setup.sh for their CI jobs, but also it definitely doesn't hurt to ping the [email protected] mailing list when these updates happen in the future anyways. Thanks.
