commit 6aa70451d81cb4e81cc9428533213d87852eb3303e39c3adc2634e9b487a65b6 [browse]
Author: Sergey Matveev
Date: 2026-10-17 09:29:48 +03:00

Fix typo

commit 4a8138b583d65214b0af97ab47817df756c58b8da4da6cfb7ec754828917b082 [browse]
Author: Sergey Matveev
Date: 2026-10-14 16:52:18 +03:00

More missing envs mention in documentation

commit 61632a26564b60f12df852b66d0987e6fd5ddd6f9e45b0e1eca64a942d1efb4d [browse]
Author: Sergey Matveev
Date: 2026-10-14 16:42:28 +03:00

Mention REDO_TRACE in documentation

commit 7e4ebeaf1acd7d52ba2e8cf3edd8c94efddfd0eeba1c50394dc4e32d235c3b87 [browse]
Author: Sergey Matveev
Date: 2026-10-14 16:39:17 +03:00

Fix typo

commit 49126a80e2232d5c4a17898abdbe58ef83ae80f949ecad269483136f94f0375f [browse]
Author: Sean E. Russell
Date: 2026-10-13 09:02:22 -07:00

Add ability to override shell invoked

REDO_SHELL sets which shell goredo uses. Some OSes change which shell
/bin/sh points to; on Arch, it's bash. On Debian (on some forks, at
least), it's dash. These shells are incompatible, esp about topics like
variable expansion. With REDO_SHELL, users can set which shell goredo
forks and ensure builds run.