John Foster <[EMAIL PROTECTED]> writes:
> Is the problem with bash 2 only the ; before the } ? Then wouldn't it be
> possible to use perl to determine if a { ??? } type construct is a
> variable replacement thingy or a block of code, and edit it accordingly?
>
> Any idea where I could get a list
Is the problem with bash 2 only the ; before the } ? Then wouldn't it be
possible to use perl to determine if a { ??? } type construct is a
variable replacement thingy or a block of code, and edit it accordingly?
Any idea where I could get a list of the syntax changes from bash 1.4.7
-> bash 2.0
On Apr 9, Paul Wade wrote
: On Wed, 9 Apr 1997, Heiko Schlittermann wrote:
:
: >
: > Or wait for a new release of the bind package ;-)
: I can't seem to find a '}' anywhere near line 120.
1 #!/bin/sh -e
2 #
3 # Debian package postinst
4 # Version 1.2
5 #
6 # R
On Wed, 9 Apr 1997, Heiko Schlittermann wrote:
> On Apr 9, John Foster wrote
> :
> : It unpacks OK, but then during the config it crashes with an unknown
> : syntax error near line 120 'done'. This is just after an esac, and
>
> : Any help at all would be nice, as I can't see anything wrong
On Apr 9, John Foster wrote
:
: It unpacks OK, but then during the config it crashes with an unknown
: syntax error near line 120 'done'. This is just after an esac, and
...
: Any help at all would be nice, as I can't see anything wrong with the
: bash script, but it's not my strongest suit anyway
Hello,
I reported this problem a few weeks ago here in this list but never got
an answer back. I manage to install bind anyway basically ignoring this
error (however, dselect still says that bind is not properly installed).
I suspect something's wrong with bash 2.0-2 though. Try some other bash.
6 matches
Mail list logo