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
dh-make-ruby
DH-MAKE-RUBY(1)DH-MAKE-RUBY(1)NAME
dh-make-ruby - build Debian source package from Ruby library
USAGE
dh-make-ruby [OPTIONS] TARBALL|DIRECTORY
DESCRIPTION
dh-make-ruby will create a basic Debian source package from a tarball named TARBALL generated with gem2tgz, or from a DIRECTORY containing
Ruby code and metadata in a .gemspec file.
OPTIONS -p PACKAGE, --package PACKAGE
Uses PACKAGE as package name. By default, new packages will be named as ruby-$gem, where $gem is the upstream name. If the package is
mainly used as a library, then it should use the default. On the other hand, if the packages is mainly used as an application, then you
should drop the ruby- prefix by using this option an explicit package u.
--ruby-versions VERSIONS
Ruby versions to build the package for. This is used to generate the X-Ruby-Versions: field in the source package, that can later be
used to tune this value. By default, gem2deb generates a package that works on all known Ruby versions, but it might be necessary to
only build the package for Ruby 1.8, for example (using --ruby-versions "ruby1.8").
-h, --help
Displays the help
-v, --version
Displays version information and exits.
SEE ALSO gem2deb(1), dh_ruby(1)COPYRIGHT AND AUTHORS
Copyright (c) 2011, Lucas Nussbaum <lucas@debian.org>
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
2012-03-06 DH-MAKE-RUBY(1)