[
https://issues.apache.org/jira/browse/DERBY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806011#action_12806011
]
Bryan Pendleton commented on DERBY-4501:
----------------------------------------
Thanks Kim and Dag for the good suggestions and extra testing.
I feel that we should treat the issue of changing the scripts to run in more
UNIX shells as a separate
enhancement, and as part of this change we should just try to document the
current scripts as
well as we can.
Unfortunately, on my system (RedHat Linux-based), the current scripts work fine
when running /bin/sh,
which perhaps is just another way of saying that /bin/sh on my system is
actually BASH, not Bourne shell,
so I don't really have access to an environment where I can work on improving
the scripts.
But if others want to work on the scripts to improve their portability to other
shells, I think that would be wonderful!
In the meantime, I'll update the docs to incorporate the good suggestions
above, and will also add
a sentence along the lines of:
The UNIX shell scripts are known to run successfully in the Bash shell, and
you may need to
modify them slightly if you are using a different UNIX shell.
I think I should probably reword the information that I added about the Bourne
shell in the previous patch,
because I can't tell if it's correct or not, since I don't think I have a true
Bourne shell to try. Instead, I'll
label the alternate sections as "using the "dot" command" and "using the
"source" command".
> CLASSPATH scripts do not work as defined in Getting Started in Derby Guide
> --------------------------------------------------------------------------
>
> Key: DERBY-4501
> URL: https://issues.apache.org/jira/browse/DERBY-4501
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.5.3.0
> Environment: Unix platforms
> Reporter: John Storta Jr.
> Assignee: Bryan Pendleton
> Priority: Minor
> Attachments: docs.diff, docs.diff, tgs26250.html, tgs26250.html
>
>
> On pages 13 and 14 of the 'Getting Started in Derby Guide', there are 3
> scripts referenced that can be used to set the CLASSPATH environment
> variable. setEmbeddedCP, setNetworkServerCP, & setNetworkClientCP. The
> documentation indicates that the appropriate script should be run
> depending on your needs.
> Running the scripts like any other script does not work.
> When a script is run, it launches a new shell for that script. The
> CLASSPATH is set within that shell. Once the script is complete, that
> shell exits and you are returned to your shell. The CLASSPATH is only
> changed for the shell that the script was running in. The CLASSPATH in
> your shell is unchanged.
> $ ${DERBY_HOME}/bin/setNetworkClientCP
> Will result in your CLASSPATH being unchanged.
> In order for CLASSPATH in your shell to be updated, you have to run the
> script from within your shell (not launch a new shell). This is done by
> 'sourcing' the script.
> $ . ${DERBY_HOME}/bin/setNetworkClientCP
> Will run the script within your shell resulting in your CLASSPATH being
> updated.
> The documentation is not clear on this.
> Bug DERBY-4500 has been opened to address a related issue that will arise
> if/when the documentation is updated to reflect that the scripts should be
> sourced rather than run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
