Mail Archives: djgpp-workers/2000/01/15/11:57:33
-: A release candidate version of Bash 2.03 is now available from:
Mark,
Some comments about the bash203b.zip archive.
First, I unzipped the file into my /djgpp tree, using defaults
for most of the environment variables:
BASH_VERSION=2.03.0(1)-release
SYSROOT=[]
HOME=[c:/]
PATH_EXPAND=[]
PATH_SEPARATOR=[;]
PATH_SLASH=[]
TMPDIR=[c:/djgpp/tmp]
TEST_FINDS_EXE=[]
1. In ./info, I ran `install-info bashref.info dir' to update my `dir'
file with the bash dir-entry. This worked, but then `info' couldn't
find `bashref.info', and I had to rename it to `bash.info' before info
could find it. I don't know if this should be fixed on the bash side
or on the info side; maybe it is easiest just to rename `bashref.*' to
`bash.*' and rebuild.
2. Shouldn't you include `bin/sh.exe' with the binary distribution,
stub-edited to point to bash?
3. Add a brief description of the purpose of `rundos.sh' to the
`readme.dos' file. You could probably just rework Eli's description
(appended below) from the mail archives:
www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/1999/02/10/06:11:57
(My own question about rundos.sh: is it provided so that .bat and .com
programs can be run from bash?)
4. (Nit-pick): was the last DJGPP-version 1.147 or 1.14.7 ?
Otherwise it looks real nice, thanks!
jeff
------
Date:
Wed, 10 Feb 1999 13:10:16 +0200 (IST)
From:
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:
eliz AT is
To:
Holger Wahlen <H DOT Wahlen AT fz-juelich DOT de>
cc:
DJGPP mailing list <djgpp AT delorie DOT com>
Subject:
Re: Running batch files under bash
In-Reply-To:
<Pine DOT GSO DOT 3 DOT 95 DOT 990209115802 DOT 22845A-100000 AT hlrz18>
Message-ID:
<Pine DOT SUN DOT 3 DOT 91 DOT 990210130953 DOT 15037C-100000 AT is>
MIME-Version:
1.0
Reply-To:
djgpp AT delorie DOT com
Thread:
Frames, NoFrames, TwoWindows
On Tue, 9 Feb 1999, Holger Wahlen wrote:
> By the way, what exactly is one supposed to do with the
> rundos.sh script that's included in bsh1147b.zip?
This script is for those DOS/Windows programs which don't understand
forward slashes, and it also undoes the effect of the SYSROOT
variable, so that the pathnames passed to DOS programs are complete
and correct.
> I've looked
> at it and seen what it does, but I haven't found any hint how
> to use it: do I always have to type "rundos foo" explicitly
Yes, you are supposed to say "rundos foo arguments..."
> or can I also tell bash somehow, for example, to call it
> automatically for .bat and .com files?
I cannot think of an automatic solution, but you could use aliases to
do that for specific programs.
- Raw text -