From: Zefram <zefram@fysh.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: Two questions
Date: Thu, 6 Apr 2000 17:44:11 +0100 (BST) [thread overview]
Message-ID: <E12dFO7-0001W8-00@crucigera.fysh.org> (raw)
In-Reply-To: <1000406155640.ZM16497@candle.brasslantern.com> from Bart Schaefer at "Apr 6, 2000 03:56:40 pm"
Bart Schaefer wrote:
>(1) I've forgotten where those filenames starting with `!' are used, and
>there's no mention of it in INSTALL or Etc/zsh-development-guide, nor in
>"configure --help" output, nor any of the other obvious places I looked.
>Will somebody who does remember what it means please document it?
Patch below. I also added a section on the development tools that are
required, to document the version requirement on autoconf.
>(2) Relying on the ability to edit config.status is bad news to begin with.
>There must be some other way to deal with this?
There isn't. I tried everything more reasonable first; there really is
no better way to handle this problem.
-zefram
Index: ChangeLog
===================================================================
RCS file: /cvsroot/zsh/zsh/ChangeLog,v
retrieving revision 1.26
diff -c -r1.26 ChangeLog
*** ChangeLog 2000/04/06 12:46:29 1.26
--- ChangeLog 2000/04/06 16:38:53
***************
*** 1,3 ****
--- 1,9 ----
+ 2000-04-06 Andrew Main <zefram@zsh.org>
+
+ * zefram1: configure.in, Etc/zsh-development-guide: List of tools
+ required for development work, and a little more conspicuous
+ explanation of the config.status hack.
+
2000-04-06 Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
* 10543: Makefile.in: avoid distcleaning Test twice
Index: configure.in
===================================================================
RCS file: /cvsroot/zsh/zsh/configure.in,v
retrieving revision 1.1.1.65
diff -c -r1.1.1.65 configure.in
*** configure.in 2000/03/25 18:04:48 1.1.1.65
--- configure.in 2000/04/06 16:38:58
***************
*** 1607,1613 ****
[test -z "$CONFIG_HEADERS" || echo > stamp-h])
dnl The standard config.status is missing some essential features.
! dnl So add them now.
[rm -f $CONFIG_STATUS.old
cp $CONFIG_STATUS $CONFIG_STATUS.old
sed '1,$s@^\( *ac_file_inputs=\).*$@\1`echo $ac_file_in | sed -e "s%^%:%" -e "s%:\\([^!]\\)% $ac_given_srcdir/\\1%g" -e "s%:!% %"`@' \
--- 1607,1613 ----
[test -z "$CONFIG_HEADERS" || echo > stamp-h])
dnl The standard config.status is missing some essential features.
! dnl So add them now. See the comment at the end of Src/mkmakemod.sh.
[rm -f $CONFIG_STATUS.old
cp $CONFIG_STATUS $CONFIG_STATUS.old
sed '1,$s@^\( *ac_file_inputs=\).*$@\1`echo $ac_file_in | sed -e "s%^%:%" -e "s%:\\([^!]\\)% $ac_given_srcdir/\\1%g" -e "s%:!% %"`@' \
Index: Etc/zsh-development-guide
===================================================================
RCS file: /cvsroot/zsh/zsh/Etc/zsh-development-guide,v
retrieving revision 1.1.1.10
diff -c -r1.1.1.10 zsh-development-guide
*** Etc/zsh-development-guide 1999/12/16 14:26:28 1.1.1.10
--- Etc/zsh-development-guide 2000/04/06 16:39:05
***************
*** 12,17 ****
--- 12,34 ----
are very simple and hopefully should make for a more orderly development
of zsh.
+ Tools
+ -----
+
+ To develop (as opposed to just build) zsh, you'll need a few specialised
+ tools:
+
+ * GNU autoconf, version 2.12 or later. (Earlier versions mostly work,
+ but part of the configuration system now relies on part of the format
+ of the config.status files that get generated. See the comments in
+ configure.in and at the end of Src/mkmakemod.sh for an explanation.)
+
+ * GNU m4. (Required by autoconf.)
+
+ * yodl.
+
+ * texi2html.
+
Patches
-------
END
next prev parent reply other threads:[~2000-04-06 16:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-06 10:42 Sven Wischnowsky
2000-04-06 15:56 ` Bart Schaefer
2000-04-06 16:44 ` Zefram [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 10:47 Two Questions Nikolai Weibull
2000-04-06 8:39 Two questions Sven Wischnowsky
2000-04-06 9:55 ` Bart Schaefer
2000-04-06 10:36 ` Andrej Borsenkow
1999-01-26 18:32 Phil Pennock
1999-01-27 6:36 ` Bart Schaefer
1999-01-27 10:59 ` Phil Pennock
1999-01-27 11:13 ` Geoff Wing
1999-01-27 11:33 ` Bruce Stephens
1999-01-27 12:46 ` Peter Stephenson
1999-01-27 11:28 ` Bruce Stephens
1999-01-27 14:11 ` Phil Pennock
1999-01-27 18:25 ` Bart Schaefer
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=E12dFO7-0001W8-00@crucigera.fysh.org \
--to=zefram@fysh.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.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).