It seems like it should be simple to symlink one file to a new file in a subdirectory.... ....without moving subdirectories.  But something about the syntax is perplexing and counter to what I would expect.  Here's a test case:mkdir tempcd tempmkdir deployecho Contents of the build file! > deploy/resources.build.phpln -s deploy/resources.build.php deploy/resources.phpcat deploy/resources.php #bad symlinkThis just creates a broken symlink!I am running this in a build environment setup script, so I want to avoid changing the current working directory if at all possible.ln -s deploy/resources.build.php resources.phpcat deploy/resources.phpAlso doesn't work because it creates the symlink in the temp directory instead of the deploy subdirectory.cd deployln -s resources.build.php resources.phpcd ..This works, but I'd prefer to know how to do it without changing directories.Using a full path like: /home/whatever/src/project/temp/stuff/temp/deploy/resources.build.phpWorks, but is unweildy and somewhat impractical, especially in a build environment where all the project stuff might be different between builds, and the like.How can I create a symlink between two files in a subdirectory, without moving into that subdirectory and out of it, and while giving the new file alias a new name?
Symlink aliasing files in subdirectories without changing current directory
directory;symlink;ln
But something about the syntax is perplexing and counter to what I would expect.The arguments for ln, in the form that you're using it, are:ln [OPTION]... [-T] TARGET LINK_NAME   (1st form)The perplexing, unintuitive thing is that when you're creating a symlink, the target argument for ln isn't expected to be a path to a file, but rather the contents of the symlink to be created.  If you think about it for a moment, it's obvious that it has to be that way.  Consider:$ echo foo >foo$ ln -s foo bar1$ ln -s $PWD/foo bar2$ cat bar1foo$ cat bar2foo$ ls -l bar1 bar2lrwxrwxrwx 1 matt matt  3 Dec 29 16:29 bar1 -> foolrwxrwxrwx 1 matt matt 29 Dec 29 16:29 bar2 -> /home/matt/testdir/fooIn that example I create 2 symlinks, named bar1 and bar2, that point to the same file.  ls shows that the symlinks themselves have different contents, though - one contains an absolute path, and one contains a relative path.  Because of this, one would continue working even if it were moved to another directory, and the other wouldn't:$ mv bar2 /tmp$ cat /tmp/bar2foo$ mv bar1 /tmp$ cat /tmp/bar1cat: /tmp/bar1: No such file or directorySo, considering that we must be able to make both relative and absolute symlinks, and even to create broken symlinks that will become un-broken if the target file is later created, the target argument has to be interpreted as freeform text, rather than the path to an already-existing file.If you want to create a file named deploy/resources.php that links to deploy/resources.build.php, you need to decide if you want to create an absolute symlink (which is resilient against the symlink being moved, but breaks if the target is moved), or a relative symlink (which will keep working as long as both the symlink and the target are moved together and maintain the same relative paths).To create an absolute symlink, you could do:$ ln -s $PWD/deploy/resources.build.php deploy/resources.phpTo create a relative one, you would first figure out the relative path from the source to the target.  In this case, since the source and target are in the same directory relative to one another, you can just do:$ ln -s resources.build.php deploy/resources.phpIf they weren't in the same directory, you would need to instead do something like:$ ln -s ../foo/f bar/bIn that case, even though foo and bar are both in your current directory, you need to include a ../ into the ln target because it describes how to find f from the directory containing b.That's an extremely long explanation, but hopefully it helps you to understand the ln syntax a little better.