public inbox for goredo-devel@lists.stargrave.org
Atom feed

From: "\"Sean E. Russell\" (ser.goredo=ser1.net) via" <goredo-devel@lists.stargrave.org>
To: "Sergey Matveev (stargrave=stargrave.org) via"
	<goredo-devel@lists.stargrave.org>
Subject: Re: [PATCH] REDO_SHELL sets which shell goredo uses
Date: Wed, 14 Oct 2026 09:08:11 -0700	[thread overview]
Message-ID: <DM4OW0P70Z8O.2BJ151O6LS5YQ@ser1.net> (raw)
In-Reply-To: <as-MN8KVjD1fyruY@stargrave.org>

On Wed Oct 14, 2026 at 7:05 AM PDT, Sergey Matveev (stargrave=stargrave.org) via wrote:
> *** ser.goredo=ser1.net via [2026-10-13 09:02]:
>>/bin/sh is not the same shell on all systems, and this can lead to non-trivial
>>`do` files failing on different machines.
>
> On POSIX systems /bin/sh is expected to be POSIX compatible.
> If one writes a shell script, then it must be POSIX one. It
> should behave on all POSIX-compatible systems the same way.

Hmm. Ok, so my bash substitutions, which I thought were POSIX, are not. TBH,
I've been using Linux since 1995 but I don't believe I've ever used raw POSIX sh
-- always csh, bash, or zsh -- so TIL.

>>This patch adds a `REDO_SHELL` environment variable.
>
> I think that this is very wrong, when people write non-POSIX compatible

Fair enough. Shebang at the beginning of every .do file works, although it's
tedious, especially with redo which tends to explode *.do files.

> under whatever /bin/sh. But at least that REDO_SHELL could be useful for
> debugging purposes, to check those shell scripts workability under
> different implementations. Applied it. Thank you!

I was just in `t/` trying to figure out how to add unit tests for the thing;
there's a few new technologies I need to learn about, like sharness, first.

>>I didn't see anywhere in the repos where the environment variables are
...
> Website is just a HTML rendered doc/ subdirectory. There is doc/Env

Ah! Excellent. Thanks, I missed that.

BTW, the Arch package for goredo was still pointing at the
www.goredo.cypherpunks.su page, which hasn't been accessible for a bit. I asked
that they rehome it to the new location -- what with all the AUR attacks,
there's some nervousness about changing upstream. Is there any way to verify
your new keys with some old one so people can feel confident that you're the
same developer?

The discussion is going on here: https://aur.archlinux.org/packages/goredo

--- SER   
Sean E. Russell (https://ser1.net)    
OpMsg: https://ser1.net/.well-known/opmsg.txt    
GPG key: https://ser1.net/.well-known/pgp.asc    
Minisign: https://ser1.net/.well-known/minisign.pub    
Age: age195vpft7nzsy83medxagqqsge0lrcuf9txe3z2znlu2wsk69cdu4sx8nfvp    

next prev parent reply	other threads:[~2026-10-14 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 16:02 [PATCH] REDO_SHELL sets which shell goredo uses ser.goredo=ser1.net via
2026-10-13 16:02 ` [PATCH] 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 ser.goredo=ser1.net via
2026-10-14 14:05 ` [PATCH] REDO_SHELL sets which shell goredo uses Sergey Matveev (stargrave=stargrave.org) via
2026-10-14 16:08   ` "Sean E. Russell" (ser.goredo=ser1.net) via [this message]
2026-10-16  8:43     ` Sergey Matveev (stargrave=stargrave.org) via
2026-10-16  9:37     ` Authenticating the tarballs and website Sergey Matveev (stargrave=stargrave.org) via
2026-10-16 23:20       ` "Sean E. Russell" (ser=ser1.net) via
2026-10-17  7:02         ` Sergey Matveev (stargrave=stargrave.org) via