Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the default shebang in docs to use /usr/bin/env #12

Open
guillep opened this issue Oct 24, 2016 · 8 comments
Open

Change the default shebang in docs to use /usr/bin/env #12

guillep opened this issue Oct 24, 2016 · 8 comments

Comments

@guillep
Copy link
Owner

guillep commented Oct 24, 2016

Like

! /usr/bin/env scale

This will make script use the scale version that is found in the path. Like that people may have different installations and use the one they want given their current configuration.

@sbragagnolo
Copy link
Collaborator

Good idea! It goes for next version, since it will use this as excuse for changing the code browser :). (Now it checks the shebang to know what scriptrunner to use as container on the browser.)

@rajula96reddy
Copy link

Hi, should it be like user specifying which version to run, before running the command?

@guillep
Copy link
Owner Author

guillep commented Mar 15, 2017

Maybe. A user wanting to use a specific version of scale write instead:

!/usr/bin/env scale
!/usr/bin/env scale-2.7
!/usr/bin/env scale-3

Of course that would require having available in PATH all scale versions. That could be done "à la" linux by adding symlinks of course

@rajula96reddy
Copy link

Maybe the scale bash script can be edited and user can be prompted for version and that specific version can be invoked. And apart from this, what more can be done for this?

@guillep
Copy link
Owner Author

guillep commented Mar 15, 2017

The main intention of this issue is to update the documentation. New features or the scale GUI support should be discussed in separate issues please.

@rajula96reddy
Copy link

Sorry.! My fault. Will do it in a new issue.

@guillep
Copy link
Owner Author

guillep commented Mar 15, 2017

Thanks, in any case, I think updating the readme would be already a good contribution.

@rajula96reddy
Copy link

Thank you. I will try to contribute to the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants