Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Getting the CVS revision of Zsh
- X-seq: zsh-users 13710
- From: Greg Klanderman <gak@xxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Getting the CVS revision of Zsh
- Date: Wed, 14 Jan 2009 12:13:41 -0500
- In-reply-to: <2d460de70901140533icf13f94yc7f63f974b236f45@xxxxxxxxxxxxxx> (Richard Hartmann's message of "Wed, 14 Jan 2009 14:33:28 +0100")
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <2d460de70901090301h6b309a7cm19c5ebfec989ff2c@xxxxxxxxxxxxxx> <2d460de70901140533icf13f94yc7f63f974b236f45@xxxxxxxxxxxxxx>
- Reply-to: gak@xxxxxxxxxxxxxx
>>>>> Richard Hartmann <richih.mailinglist@xxxxxxxxx> writes:
> % echo $ZSH_PATCHLEVEL
> 1234
To me, "patchlevel" indicates the patch version of a release, i.e. the
third number in ZSH_VERSION.
Something like ZSH_VCSREVISION to me would be a much better name, or
ZSH_CVSREVISION if you don't care about being version control system
neutral.
The other question I had on this is whether ChangeLog is necessarily
updated with every checkin to zsh source code?
> % echo $ZSH_RELEASE
> 4.3.10
Seems reasonable. You really should just need a boolean value, as
ZSH_VERSION better be the same when ZSH_RELEASE is set.
> PS: Maybe there is a clean way in current zsh to do this?
Check that there's not a "-" in ZSH_VERSION?
greg
Messages sorted by:
Reverse Date,
Date,
Thread,
Author