public inbox for goredo-devel@lists.stargrave.org
Atom feed
From: "Sergey Matveev (stargrave=stargrave.org) via" <goredo-devel@lists.stargrave.org>
To: "\"Sean E. Russell\" (ser.goredo=ser1.net) via"
<goredo-devel@lists.stargrave.org>
Subject: Re: [PATCH] REDO_SHELL sets which shell goredo uses
Date: Fri, 16 Oct 2026 11:43:57 +0300 [thread overview]
Message-ID: <atHjmAB2oiItxVJG@stargrave.org> (raw)
In-Reply-To: <DM4OW0P70Z8O.2BJ151O6LS5YQ@ser1.net>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
*** "Sean E. Russell" (ser.goredo=ser1.net) via [2026-10-14 09:08]:
>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.
I think most people use those kind of shells for interactive purposes.
But ((POSIX) shell) scripts are different things, of course. Personally
I use zsh, write some "#!/usr/bin/env zsh"-shebanged scripts for
convenience, but have to use "#!/bin/sh" to write portable POSIX ones.
Debian is a well-known distribution that started to actively clean out
so-called shell scripts, which were in fact full of bash-isms (so dash,
checkbashisms utilities were created). ALT Linux was another one, which
was aggressive in that task.
>Fair enough. Shebang at the beginning of every .do file works, although it's
>tedious, especially with redo which tends to explode *.do files.
Definitely. So if user is aware that he is writing non-POSIX .do
scripts, but willing to do so for convenience, REDO_SHELL would be
indeed helpful.
--
* Origin: Stargrave's homepage http://www.stargrave.org/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]
next prev parent reply other threads:[~2026-10-16 8:44 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
2026-10-16 8:43 ` Sergey Matveev (stargrave=stargrave.org) via [this message]
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