Patrick Georgi via coreboot <coreboot@coreboot.org> writes: > Am Di., 9. Feb. 2021 um 11:34 Uhr schrieb Arthur Heymans <arthur.heym...@9elements.com>: > > So TL;DR: > - Is (temporarily) adding a tool to the blobs repo ok? > > If it matches the requirements of the blobs repo wrt. license terms and documentation, I don't see why not from a formal perspective. > It's telling though (in the sense of a Freudian slip) that you put the "temporarily" in parentheses already: interim solutions like these tend to survive > their best due date ;-)
I was told this typically takes Intel a few months. > - Is integrating an (optional) not yet open tool into the build system ok? > > This one is IMHO the bigger issue: that tool will only run on Linux/x86(-64?), and probably only with a select set of libc implementations. While we > have portability issues every now and then, they're always accidentally introduced because our testing isn't good enough while adding this to the > build flow deliberately makes all other platforms second tier build hosts. > Good point! Tools build with go include the go runtime so they should be fully standalone. Adding different ARCH + OS is very easy with go, so adding other platforms can be done very quickly if desired. Kind regards -- ============== Arthur Heymans _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
