On 13.03.22 08:28, Anastasia Klimchuk wrote:
Some of the things in the first list that I wanted to ask about:
cb973683 Added partial meson support which confuses package main- tainers. Should we remove it from or disable CLI building on release branches?”
Oh, we are using meson in the chromium tree to build everything. I added a topic to the meeting agenda about Meson and Makefile, although it overflowed to the next meeting.
Also I understand Meson already got into v1.2? I thought the next version is based on the previous?
Yes, but I hope that doesn't mean we can't revert problems :)
The `meson.build` made it into v1.2, that is right but turned out to cause more trouble than was expected. OS package maintainers quickly adopted it without any second thought. And then all their packages had issues because the `meson.build` did some things wrong (no version in- formation in the binary for instance, no man page in the package, CLI options not working). Almost nobody tried to build the flashrom CLI with Meson before. The known issues are fixed, but so far we only know that it works on x86 and ARM with Linux (that's likely less than 10% of what is expected to work with the Makefile).
My latest idea about this is that we could add an option (e.g. `inofficial`) and a whitelist of known working platforms. Such that one would have to literally state they want an inofficial binary to build on a platform with unknown status.
ad08aef6 Undocumented programmer. disable? drop from realease branch?
I looked that is about raiden debug programmer. If it is undocumented, can we document?
Hopefully. IMO, the minimum for a new programmer to be accepted upstream is a section in the manpage, including documentation about programmer parameters. With such documentation at hand, we could even start to re- view the code ;)
I had a look at the comment on top of `raiden_debug_spi.c` right now. I knew it was attached over USB, but it seems that the other end goes directly to the target device (not any kind of dongle between two computers). If that is the case, it would be important to know what Chromebook (I guess) models support it.
Nico