On Fri, Oct 23, 2015 at 8:39 AM Patrick Georgi pgeorgi@google.com wrote:
It's more trivial not to have a tool in the first place. It's also more trivial not to add a new dependency to our build process. Especially a dependency that is lacking in portability (ie. users can't build coreboot anymore because they can't run go)
Sorry, but no.
Actually the idea crossed my mind because I just saw a different tool hit the tree yesterday that was written in ... guess what language?
I would have accepted the 'go is not supported' argument a year ago. Now? It's everywhere.
But, ok, ship binaries. I guess we'll grow the blobs.
ron