Skip to content

Tags: u-root/gobusybox

Tags

v0.3.0

Toggle v0.3.0's commit message
Lock mvdan/sh to v3.11.0

v3.13 has a serious bug, which is that it names kill as
a builtin but does not implement it.

Which would not be a problem, save that mkuimage imports gobusybox,
and that cascades to u-root, and u-root ends up using v3.13.1 of
mvdan/sh, which has the bug.

It would be much better, I suspect, to stop using shell.Fields
in gobusybox, and just forgo having working shell expansion.

Using mvdan/sh in gobusybox causes trouble 2 repos to our left ...

mvdan/sh might need to be split up as grpc was a while back.

Just getting a bunch of broken code, when all you want is shell expansion,
is a problem.

Signed-off-by: Ronald G Minnich <rminnich@gmail.com>

src/v0.3.0

Toggle src/v0.3.0's commit message
Lock mvdan/sh to v3.11.0

v3.13 has a serious bug, which is that it names kill as
a builtin but does not implement it.

Which would not be a problem, save that mkuimage imports gobusybox,
and that cascades to u-root, and u-root ends up using v3.13.1 of
mvdan/sh, which has the bug.

It would be much better, I suspect, to stop using shell.Fields
in gobusybox, and just forgo having working shell expansion.

Using mvdan/sh in gobusybox causes trouble 2 repos to our left ...

mvdan/sh might need to be split up as grpc was a while back.

Just getting a bunch of broken code, when all you want is shell expansion,
is a problem.

Signed-off-by: Ronald G Minnich <rminnich@gmail.com>

v0.2.0

Toggle v0.2.0's commit message
Add codecov config

Signed-off-by: Chris Koch <chrisko@google.com>

v0.1.0

Toggle v0.1.0's commit message
README: detail how to use bazel rule [skip ci]

Signed-off-by: Chris Koch <chrisko@google.com>