Hi,
I am currently writing BASH shell scripts. I am using BASH on a Powerbook G4 running Leopard. Could somebody please explain the difference between
#!/bin/bash and #!/bin/sh?
I have been using the latter (#!/bin/sh), and things have been working fine. But is that the correct one to use... (9 Replies)
Do we need to include the exclamatory mark in the shebang line??:confused:
What if we dont include it??:eek:
Actually what shebang line implies when we run a script??
shebang line--> #!/bin/ksh :p (6 Replies)
*** EDIT: I found something close to my solution under an IIS 7 Module Handle.*****
(Non-Homework question, simply an ease of use one)
Odd question here and maybe its my newness to cgi/Perl, but is it possible to have 2 shebang lines?
I write an test a ton of my homework code on my windows... (1 Reply)
Hi,
I always thought that #!/usr/bin/ksh means that the script would be executed in korn shell i.e. when we'll execute the script with this line as the very first line then the shell spawns a korn shell (in this case as we are using #!/usr/bin/ksh ) and the script gets executed.
But I am... (7 Replies)
Hi ,
I know about the shebang line in shell scripting. Just want to know whether is there any difference in execution of the program by keeping and not keeping the shebang line. Because without shebang line also the script is working. correct me if am wrong. Any help on this will be helpful (5 Replies)
I see lot of ad-hoc shell scripts in our servers which don't have a shebang at the beginning .
Does this mean that it will run on any shell ?
Is it a good practice to create scripts (even ad-hoc ones) without shebang ? (16 Replies)
Hello All,
I was writing a Bash shell script that will be executed on both an AIX server (/usr/bin/ksh) and a SLES server (/bin/bash). The AIX server
has Bash installed at "/usr/bin/bash", which is in a different dir then the SLES server.
So basically I am writing the script on the SLES... (4 Replies)
Discussion started by: mrm5102
4 Replies
LEARN ABOUT DEBIAN
ruby-build
RUBY-BUILD(1)RUBY-BUILD(1)NAME
ruby-build - compile and install Rubies
SYNOPSIS
ruby-build [-v|--verbose] [-k|--keep] definition prefix
ruby-build --definitions
ruby-build --version
ruby-build [-h|--help]
rbenv install [-k|--keep] definition
DESCRIPTION
ruby-build provides a simple way to compile and install different versions of Ruby on UNIX-like systems.
ruby-build downloads, builds and installs the Ruby version specified in a definition into a prefix directory. Definitions can be chosen
from the list of installed definitions or by specifying a file path for a definition.
rbenv(1) users can also use the provided rbenv install command, which installs Rubies into the rbenv directory.
OPTIONS --definitions
List available definitions.
-k, --keep
Don't delete source code after installation.
-v, --verbose
Display compiler messages on standard output.
--version
Show ruby-build version and exit.
-h, --help
Show usage information and exit.
EXAMPLES
Install Ruby 1.9.3 (MRI, patch level 0) to ~/rubies/mri-1.9.3
$ ruby-build 1.9.3-p0 ~/rubies/mri-1.9.3
Install Ruby Enterprise Edition 1.8.7 (patch level 2011.03) for rbenv(1):
$ rbenv install ree-1.8.7-2011.03
Install Ruby from a custom definition into ~/your-ruby:
$ rbenv install /path/to/your/own/ruby/definition ~/your-ruby
ENVIRONMENT
CC Sets the path to the C compiler.
CONFIGURE_OPTS
Options that are passed to configure when building a Ruby.
MAKE_OPTS
Options that are passed to make when building a Ruby.
MAKEOPTS
Used instead of MAKE_OPTS when MAKE_OPTS is not defined.
TMPDIR Sets the location where ruby-build stores temporary files.
RUBY_BUILD_BUILD_PATH
Sets the location in which sources are downloaded and built.
AUTHORS
ruby-build is developed by Sam Stephenson <sam@37signals.com>.
This man page was written for the Debian GNU/Linux distribution by Sebastian Boehm <sebastian@sometimesfood.org> but may be used by others.
SEE ALSO rbenv(1)
June 2012 RUBY-BUILD(1)