[
https://issues.apache.org/jira/browse/WHIRR-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209239#comment-13209239
]
Marco Didonna commented on WHIRR-507:
-------------------------------------
We can definitely use a readlink if available, but the problem is the plan B in
case readlink is not available. I did use that so question but basically all
answers use readlink. There's an elegant solution in the scala script but I'm
afraid it would be licence violation if we used it
> Make whirr script executable from any path
> ------------------------------------------
>
> Key: WHIRR-507
> URL: https://issues.apache.org/jira/browse/WHIRR-507
> Project: Whirr
> Issue Type: Improvement
> Affects Versions: 0.7.0
> Environment: Linux (Ubuntu 11.04)
> Reporter: Marco Didonna
> Assignee: Marco Didonna
> Priority: Minor
> Labels: bash, script
> Fix For: 0.8.0
>
> Attachments: whirr, whirr.noreadlink, whirr.readlink,
> whirr_script.patch
>
>
> I personally find very painful to be forced to call whirr script using its
> whole path. I'd prefer to add whirr script to my $PATH env variable so that I
> can call whirr from anywhere. I've modified the whirr script according to
> this purpose.
> I've created two version of the modified script:
> * one that uses the readlink command
> * one that doesn't used the former command.
> I only tested under Ubuntu 11.04 so I've no idea whether or not the readlink
> command is available on other distros. So please test and comment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
