db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-677) ksh scripts should be written in a more portable way
Date Thu, 03 Nov 2005 17:52:44 GMT
     [ http://issues.apache.org/jira/browse/DERBY-677?page=all ]

Knut Anders Hatlen updated DERBY-677:

    Attachment: DERBY-677.diff

Attached a patch which fixes the scripts.

% svn stat
M      frameworks/NetworkServer/bin/ij.ksh
M      frameworks/NetworkServer/bin/setNetworkServerCP.ksh
M      frameworks/NetworkServer/bin/setNetworkClientCP.ksh
M      frameworks/embedded/bin/setEmbeddedCP.ksh

> ksh scripts should be written in a more portable way
> ----------------------------------------------------
>          Key: DERBY-677
>          URL: http://issues.apache.org/jira/browse/DERBY-677
>      Project: Derby
>         Type: Bug
>   Components: Demos/Scripts
>     Versions:,
>     Reporter: Knut Anders Hatlen
>     Assignee: Knut Anders Hatlen
>     Priority: Minor
>  Attachments: DERBY-677.diff
> The ksh scripts in the frameworks directory are written in a way which
> is not totally portable. They use a syntax that is specific to ksh and
> not understood by the standard Bourne shell. This prevents some
> variants of Unix from running the scripts when you have the scripts'
> path in your PATH environment variable.
> These commands work:
>   ksh /path/to/scripts/ij.ksh
>   bash /path/to/scripts/ij.ksh
> These commands might not work on some platforms:
>   sh /path/to/scripts/ij.ksh
>   /path/to/scripts/ij.ksh
>   ij.ksh   # might not work even if /path/to/scripts is in PATH
> The syntax that is not portable is
>   export VAR=value
> Rewriting it to
>   VAR=value
>   export VAR
> would make the scripts portable to all shells in the Korn and Bourne
> shell family.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message