From: Clint Adams <clint@zsh.org>
To: zsh-workers@sunsite.dk
Subject: PATCH: remove ZSH_VERSIONSUFFIX
Date: Sun, 3 Feb 2008 13:14:01 -0500 [thread overview]
Message-ID: <20080203181401.GA15120@scowler.net> (raw)
Since this doesn't work as-is, I'm backing it out and will probably
do sed substitutions on Config/version.mk as needed.
Index: configure.ac
===================================================================
RCS file: /cvsroot/zsh/zsh/configure.ac,v
retrieving revision 1.91
diff -u -r1.91 configure.ac
--- configure.ac 1 Feb 2008 11:31:36 -0000 1.91
+++ configure.ac 3 Feb 2008 18:11:52 -0000
@@ -31,7 +31,6 @@
dnl What version of zsh are we building ?
. ${srcdir}/Config/version.mk
-VERSION="$VERSION$ZSH_VERSIONSUFFIX"
echo "configuring for zsh $VERSION"
dnl ----------------------------------------------
Index: Etc/zsh-development-guide
===================================================================
RCS file: /cvsroot/zsh/zsh/Etc/zsh-development-guide,v
retrieving revision 1.17
diff -u -r1.17 zsh-development-guide
--- Etc/zsh-development-guide 22 Jan 2008 01:59:26 -0000 1.17
+++ Etc/zsh-development-guide 3 Feb 2008 18:11:52 -0000
@@ -856,13 +856,3 @@
distribution, but that need to be present in the CVS tree. This
variable is not used by the zsh build process and is present for
the convenience of external checks.
-
-Version Suffixes
-----------------
-The configure script reads the version number from Config/version.mk.
-If the environment variable ZSH_VERSIONSUFFIX is set, the string
-contained therein will be appended to the version string. For example,
-if Config/version.mk contains "VERSION=4.3.4-dev-7" and
-ZSH_VERSIONSUFFIX is set to "-ca", $ZSH_VERSION in the shell built from
-that run will equal "4.3.4-dev-7-ca". Caution is recommended when
-using this feature, as is-at-least may misunderstand your conventions.
reply other threads:[~2008-02-03 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080203181401.GA15120@scowler.net \
--to=clint@zsh.org \
--cc=zsh-workers@sunsite.dk \
/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).