Bdtyktl

Be careful! ./ and source are not quite the same.

• 
  ./script runs the script as an executable file, launching a new shell to run it


• 
  source script reads and executes commands from filename in the current shell environment

Note: ./script is not . script, but . script == source script

https://askubuntu.com/questions/182012/is-there-a-difference-between-and-source-in-bash-after-all?lq=1

It is useful to know the 'type' command:

> type source

source is a shell builtin

whenever something is a shell builtin it is time to do man bash.

. (a period) is a bash shell built-in command that executes the commands from a file passed as argument, in the current shell. 'source' is a synonym for '.'.

From Bash man page:

. filename [arguments]

source filename [arguments]

       Read  and  execute  commands  from filename in the current shell

       environment and return the exit status of the last command  exe‐

       cuted from filename.  If filename does not contain a slash, file

       names in PATH are used to find the  directory  containing  file‐

       name.   The  file  searched  for in PATH need not be executable.

       When bash is  not  in  posix  mode,  the  current  directory  is

       searched  if no file is found in PATH.  If the sourcepath option

       to the shopt builtin command is turned  off,  the  PATH  is  not

       searched.   If any arguments are supplied, they become the posi‐

       tional parameters when  filename  is  executed.   Otherwise  the

       positional  parameters  are unchanged.  The return status is the

       status of the last command exited within the  script  (0  if  no

       commands  are  executed),  and false if filename is not found or

       cannot be read.

'source' is the long version of '.' command. On the bash prompt one can do:

source ~/.bashrc

to reload your (changed?) bash setting for current running bash.

Short version would be:

. ~/.bashrc

The man page:

. filename [arguments]

source filename [arguments]

    Read and execute commands from filename in the current shell environment and

    return the exit status of the last command executed from filename. If 

    filename does not contain a slash, file names in PATH are used to find the

    directory containing filename. The file searched for in PATH need not be

    executable. When bash is not in posix mode, the current directory is

    searched if no file is found in PATH. If the sourcepath option to the short

    builtin command is turned off, the PATH is not searched. If any arguments

    are supplied, they become the positional parameters when filename is

    executed. Otherwise the positional parameters are unchanged. The return 

    status is the status of the last command exited within the script (0 if no

    commands are executed), and false if filename is not found or cannot be

    read. 

source command executes the provided script (executable permission is not mandatory) in the current shell environment, while ./ executes the provided executable script in a new shell.

source command do have a synonym . filename.

To make it more clear, have a look at the following script, which sets the alias.

make_alias

#! /bin/bash



alias myproject='cd ~/Documents/Projects/2015/NewProject'

Now we have two choices to execute this script. But with only one option, the desired alias for current shell can be created among these two options.

Option 1: ./make_alias

Make script executable first.

chmod +x make_alias

Execute

./make_alias

Verify

alias

Output

**nothing**

Whoops! Alias is gone with the new shell.

Let's go with the second option.

Option 2: source make_alias

Execute

source make_alias

or

. make_alias

Verify

alias

Output

alias myproject='cd ~/Documents/Projects/2015/NewProject'

Yeah Alias is set.

When in doubt, the best thing to do is use the info command:

[root@abc ~]# info source



BASH BUILTIN COMMANDS

       Unless otherwise noted, each builtin command documented in this section

       as accepting options preceded by - accepts -- to signify the end of the

       options.   The  :, true, false, and test builtins do not accept options

       and do not treat -- specially.  The exit, logout, break, continue, let,

       and  shift builtins accept and process arguments beginning with - with-

       out requiring --.  Other builtins that accept  arguments  but  are  not

       specified  as accepting options interpret arguments beginning with - as

       invalid options and require -- to prevent this interpretation.

       : [arguments]

              No effect; the command does nothing beyond  expanding  arguments

              and  performing any specified redirections.  A zero exit code is

              returned.



        .  filename [arguments]

       source filename [arguments]

              Read and execute commands from filename  in  the  current  shell

              environment  and return the exit status of the last command exe-

              cuted from filename.  If filename does not contain a slash, file

              names  in  PATH  are used to find the directory containing file-

              name.  The file searched for in PATH  need  not  be  executable.

              When  bash  is  not  in  posix  mode,  the  current directory is

              searched if no file is found in PATH.  If the sourcepath  option

              to  the  shopt  builtin  command  is turned off, the PATH is not

              searched.  If any arguments are supplied, they become the  posi-

              tional  parameters  when  filename  is  executed.  Otherwise the

              positional parameters are unchanged.  The return status  is  the

              status  of  the  last  command exited within the script (0 if no

              commands are executed), and false if filename is  not  found  or

              cannot be read.

Type the command "help source" in your shell.

You will get output like this:

source: source filename [arguments]



Execute commands from a file in the current shell.



Read and execute commands from FILENAME in the current shell.  The

entries in $PATH are used to find the directory containing FILENAME.

If any ARGUMENTS are supplied, they become the positional parameters

when FILENAME is executed.



Exit Status:

Returns the status of the last command executed in FILENAME; fails if

FILENAME cannot be read.

From the Linux Documentation Project, Advanced Bash Scripting Guide,

Chapter 15 - Internals Commands and Builtins:

source, . (dot command):

This command, when invoked from the command-line, executes a script. Within a script, a source file-name loads the file file-name. Sourcing a file (dot-command) imports code into the script, appending to the script (same effect as the #include directive in a C program). The net result is the same as if the "sourced" lines of code were physically present in the body of the script. This is useful in situations when multiple scripts use a common data file or function library.

If the sourced file is itself an executable script, then it will run, then return control to the script that called it. A sourced executable script may use a return for this purpose.

So, for those familiar with C programming language, sourcing a file has an effect similar to the #include directive.

Note also that you may pass positional arguments to the file being sourced, like:

$ source $filename $arg1 arg2

It should be noted that although being an awesome command, neither source nor its shorthand of . would source more than one file, meaning

source *.sh

or

. script1.sh script2.sh

will not work.

We can fall back using for loops, but it would issue the executable many times, creating multiple commands or issue of it.

Conclusion: source doesn't take multiple files as input. The argument has to be one.

Which sucks IMHO.

With source you can pass variables or functions from another file in to your script and use them without having to write them again.

F.I:

#!/bin/bash



source /etc/environment



source /myscripts/jetty-common/config/jetty-functions.sh

Cheers