On 2021/03/28 20:22, Matthew Martin wrote: > On Sat, Mar 27, 2021 at 09:36:24PM +0100, Christian Weisgerber wrote: > > Matthew Martin: > > > > > A while back [1] it was noted zsh's $OSTYPE is out of sync with the OS > > > version. > > > > > > 1: https://marc.info/?l=openbsd-ports&m=160940571013139&w=2 > > > > I don't think there's a problem to solve. > > > > OSTYPE describes the operating system this instance of zsh (or bash) > > was compiled on. There are all sorts of programs that include this > > information, e.g. mutt -v. > > In practice OSTYPE is used to determine the operating system on which > the script is running. For example completers will consult OSTYPE to > determine which options a utility supports; some completers will match > against the version number to further refine the completions provided.
That doesn't make much sense to me - that is exactly what uname is for. If OSTYPE was meant to be the same as uname, why didn't upstream have it call uname(3) instead of being baked-in to the binary? > However, there are no completers for OpenBSD which depend on the version > number at present and I at least only target -current when adding or > updating completers. > > I see it as a matter of correctness, and at least one user has noticed > the discrepancy. > > I would be happy to send in REVISION bump patches each -beta crank if > that's acceptable; though I also understand not wanting the churn.
