From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: configure-more.zip
Date: Sat, 02 Jul 2005 13:57:10 +0200 [thread overview]
Message-ID: <upsu1qv3d.fsf@gnu.org> (raw)
In-Reply-To: <42C65DE9.6010703@student.lu.se> (message from Lennart Borgman on Sat, 02 Jul 2005 11:27:05 +0200)
> Date: Sat, 02 Jul 2005 11:27:05 +0200
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
>
> Since I once again missed that 'cvs update -kb' I decided to do
> something about it. I have attached a bat-file that checks for this and
> also for the existence of 'find' and 'xargs' which I believe also are
> needed to build Emacs.
<rant>
Why send it as a .zip file in a binary attachment, when all you want
to send is plain text for inclusion in configure.bat?
</rant>
> This runs under cmd.exe and it also seems to work under command.com.
>
> Could we please augment configure.bat with this? ;-)
Thanks.
I must say that I don't like this solution too much. First, the
problems you are trying to solve are only relevant for people who
build CVS Emacs. It is IMHO a bad idea to frighten users who are
building from a released tarball by warning them against non-existent
problems or asking them to install unneeded utilities.
Checking the line endings with "grep -P" is also less than ideal: some
users might have a Grep that is not recent enough to support -P, or
even a Grep that is not a GNU Grep. AFAICS, we didn't even require to
have Grep installed until now.
Finally, I think the Windows build needs neither `find' nor `xargs'.
Can you tell where you saw them used?
Therefore, I suggest the following strategy for solving the -kb issue:
put a small C program into the nt subdirectory which would read
nt/configure.bat, nt/nmake.defs, and nt/makefile.w32-in in binary mode
and make sure they have the right line endings; if they don't, this
program would fail. Then have this program invoked by "make bootstrap"
in the nt directory.
Would you like to implement this solution?
next prev parent reply other threads:[~2005-07-02 11:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 9:27 configure-more.zip Lennart Borgman
2005-07-02 10:47 ` configure-more.zip Jason Rumney
2005-07-02 11:00 ` configure-more.zip Lennart Borgman
2005-07-02 11:57 ` Eli Zaretskii [this message]
2005-07-02 11:12 ` configure-more.zip Lennart Borgman
2005-07-02 13:20 ` configure-more.zip Eli Zaretskii
2005-07-02 13:32 ` configure-more.zip Lennart Borgman
2005-07-02 16:57 ` configure-more.zip Eli Zaretskii
2005-07-03 2:22 ` configure-more.zip Kevin Gallagher
2005-07-03 6:22 ` configure-more.zip Eli Zaretskii
2005-07-03 6:24 ` configure-more.zip Kevin Gallagher
2005-07-03 10:42 ` configure-more.zip Glenn Morris
2005-07-03 16:01 ` configure-more.zip Eli Zaretskii
2005-07-02 17:05 ` configure-more.zip Stefan Monnier
2005-07-02 20:15 ` configure-more.zip Jason Rumney
2005-07-03 6:12 ` configure-more.zip Eli Zaretskii
2005-07-03 7:38 ` configure-more.zip Lennart Borgman
2005-07-03 16:14 ` configure-more.zip Eli Zaretskii
2005-07-03 15:28 ` configure-more.zip Lennart Borgman
2005-07-03 18:54 ` configure-more.zip Eli Zaretskii
2005-07-03 18:17 ` configure-more.zip Lennart Borgman
2005-07-03 19:22 ` configure-more.zip Jason Rumney
2005-07-03 10:31 ` configure-more.zip Juanma Barranquero
2005-07-03 16:15 ` configure-more.zip Eli Zaretskii
2005-07-03 16:43 ` configure-more.zip Juanma Barranquero
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=upsu1qv3d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.