On 04/02/2014 13:24, Anatol Pomozov wrote: > The only thing that comes to my mind is if the folder where we 'cd' > before doing 'patch' is a symlink. In this case '..' will differ from > $srcdir. But unpacked source directory can't be a symlink, is it?
I didn't read anything letting assume that a source cannot be a symlink to a directory. So it can be done manually. As far I remember, I got this issue one time, when I manually symlinked the kernel linux directory in my $startdir directory to a shared copy. > > I do not mind to change it to the longer version "$srcdir/foo" if this > is a recommended way to do, but first I want to know why it is recommended. > Although it's not strictly recommended (we lack of official recommendation?), this way works in all cases. I have to confess that I have smoothly switched all my relative path to full path since I got the previous issue. Cheers, -- Sébastien "Seblu" Luttringer https://seblu.net GPG: 0x2072D77A
signature.asc
Description: OpenPGP digital signature
