* Charles Wilson wrote on Tue, Apr 05, 2011 at 04:15:02PM CEST:
> On 4/5/2011 9:21 AM, Arnaud Charlet wrote:
> >> I'm one of the MSys "devs" (if you want to call the sporadic process of
> >> updating MSys "development"). I'll take a look at implementing
> >> ln -s file dir
> >> as synonymous with
> >> ln -s file dir/basename-of-file
> >> in the next few days.
Please use LN_S *only* in the way that it is documented. Let me quote 'info
Autoconf --index LN_S':
-- Macro: AC_PROG_LN_S
If `ln -s' works on the current file system (the operating system
and file system support symbolic links), set the output variable
`LN_S' to `ln -s'; otherwise, if `ln' works, set `LN_S' to `ln',
and otherwise set it to `cp -p'.
If you make a link in a directory other than the current
directory, its meaning depends on whether `ln' or `ln -s' is used.
To safely create links using `$(LN_S)', either find out which form
is used and adjust the arguments, or always invoke `ln' in the
directory where the link is to be created.
In other words, it does not work to do:
$(LN_S) foo /x/bar
Instead, do:
(cd /x && $(LN_S) foo bar)
Thanks,
Ralf
