zsh-users
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: zzapper <david@rayninfo.co.uk>
Cc: zsh-users@zsh.org
Subject: Re: What is considered minimum version of zsh?
Date: Fri, 24 Oct 2014 23:09:36 +0000	[thread overview]
Message-ID: <20141024230936.GA15743@tower.spodhuis.org> (raw)
In-Reply-To: <XnsA3D07AF7DE2A3davidrayninfocouk@80.91.229.13>

On 2014-10-24 at 11:05 +0000, zzapper wrote:
> I was using I believe version v4.2.6 on Centos 5 and found that some 
> essential feature was missing. Yum didnt have an upgrade . In the end it 
> was easy enough to download a newer version and Make it.
> 
> But if you cant have the latest version what is your minimum version?

Others have noted that this is difficult to interpret meaningfully.

You probably want to:

  autoload +X is-at-least

which will let you do things like:

  is-at-least 4.3.7 && zmodload -mF zsh/files 'b:zf_*'
  is-at-least 4.3.6 && zmodload -ab -i zsh/stat zstat

After that, you can craft startup files to be somewhat portable.

Somewhere in the middle of the 4.3.x series (.5, .6?) zsh started being
usable as /bin/sh on various Linux systems, because we added features
like =~ and added flags to pre-command modifiers, to improve
compatibility with people ssh'ing into boxes and making shell
assumptions.

The zsh maintainers moved to 5.0.x as a numbering scheme to make a
public statement that this is the _stable_ branch of the shell, where
4.3, technically a development branch, had been in fact the stable
bug-fixed branch.

Either you can control the versions of the software available on all
affected systems, so can make sure you're as up-to-date as you need; or
you can't, and the question is meaningless because you have to work with
what you have.  The only middle-ground here is if you're trying to argue
that someone else should be doing work to upgrade, to your benefit.  In
that scenario, I recommend either making sure you're using version
guards such as is-at-least or learning about compiled programming
languages, where you have far fewer issues with run-time dependencies.

-Phil


      parent reply	other threads:[~2014-10-24 23:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 11:05 zzapper
2014-10-24 11:28 ` Marko Vihoma
2014-10-24 11:34 ` Peter Stephenson
2014-10-24 11:41 ` Clint Hepner
2014-10-24 23:09 ` Phil Pennock [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141024230936.GA15743@tower.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=david@rayninfo.co.uk \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).