Message-ID: <3E28677A.7070804@mif.vu.lt>
Date: Fri, 17 Jan 2003 21:28:42 +0100
From: Laurynas Biveinis <laurynas DOT biveinis AT mif DOT vu DOT lt>
Organization: VU MIF
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: lt, en, en-us
MIME-Version: 1.0
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
CC: DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject: Re: [Fwd: Bugs in __solve_symlinks]
References: <3E270365 DOT 372459D1 AT phekda DOT freeserve DOT co DOT uk> <3E273A88 DOT 6050403 AT mif DOT vu DOT lt> <3E273F69 DOT F42991B2 AT phekda DOT freeserve DOT co DOT uk>
In-Reply-To: <3E273F69.F42991B2@phekda.freeserve.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Jan 2003 19:26:48.0881 (UTC) FILETIME=[6152BA10:01C2BE5E]
Reply-To: djgpp-workers AT delorie DOT com

>     HERE=`pwd`
>     ln -s /dev/env/FOO link
>     export FOO=../../somefile
>     echo Hello > $FOO
>     cat link
>     cd ..
>     cat link
> 
> I don't think this will work, because the __solve_symlinks CVS code does not
> resolve /dev/env/* inline. It will get the filename from link and restart the
> resolution with /dev/env/FOO rather than `pwd`/$FOO. At least, that's how I
> think it will work.

I have not looked if it *should* work, but I've tried it and it did :) I 
guess it's because my code never goes back in path (just adds to it or 
discards completely).

--
Laurynas