I have a Bash script that needs to know its full path. I'm trying to find a broadly-compatible way of doing that without ending up with relative or funky-looking paths. I only need to support Bash, not sh, csh, etc.
What I've found so far:
The accepted answer to Getting the source directory of a Bash script from within addresses getting the path of the script via
dirname $0
, which is fine, but that may return a relative path (like.
), which is a problem if you want to change directories in the script and have the path still point to the script's directory. Still,dirname
will be part of the puzzle.The accepted answer to Bash script absolute path with OS X (OS X specific, but the answer works regardless) gives a function that will test to see if
$0
looks relative and if so will pre-pend$PWD
to it. But the result can still have relative bits in it (although overall it's absolute) — for instance, if the script ist
in the directory/usr/bin
and you're in/usr
and you typebin/../bin/t
to run it (yes, that's convoluted), you end up with/usr/bin/../bin
as the script's directory path. Which works, but...The
readlink
solution on this page, which looks like this:# Absolute path to this script. /home/user/bin/foo.sh SCRIPT=$(readlink -f $0) # Absolute path this script is in. /home/user/bin SCRIPTPATH=`dirname $SCRIPT`
But
readlink
isn't POSIX and apparently the solution relies on GNU'sreadlink
where BSD's won't work for some reason (I don't have access to a BSD-like system to check).
So, various ways of doing it, but they all have their caveats.
What would be a better way? Where "better" means:
- Gives me the absolute path.
- Takes out funky bits even when invoked in a convoluted way (see comment on #2 above). (E.g., at least moderately canonicalizes the path.)
- Relies only on Bash-isms or things that are almost certain to be on most popular flavors of *nix systems (GNU/Linux, BSD and BSD-like systems like OS X, etc.).
- Avoids calling external programs if possible (e.g., prefers Bash built-ins).
- (Updated, thanks for the heads up, wich) It doesn't have to resolve symlinks (in fact, I'd kind of prefer it left them alone, but that's not a requirement).
dirname $0
&& pwd)" ... which does not match your summary "getting the path of the script via dirname $0"and does not as you say "return a relative path".) – Trevor Boyd Smith$0
). This question is specifically absolute path, which is different. – wisbucky