Re: [Bug-stow] -t does not seem to work for -D in neither 1.3 or 1.3.3

[Harald Kirsch]

On Sat, Feb 09, 2002 at 12:56:02AM +0100, Gaël Roualland wrote:
> Gaël Roualland a écrit :
> > 
> > Harald Kirsch a écrit :
> > >
> > > Below I try to give you as much info as I can:
> > >
> > > First the setup of the storage area:
> > >
> > > % pwd
> > > /projects/bi/TextMining/Linux/stow
> > > [...]
> > >
> > > Now for the target. You can see that everything is linked nicely to
> > > the stow-area. There is also a bunch of links in lib.
> > >
> > > % ll ~/tmp/ggg
> > > total 16
> > > drwxr-xr-x    3 kirschh  user           50 Feb  8 13:59 ./
> > > drwxrwxr-x   19 kirschh  user        12288 Feb  8 14:06 ../
> > > lrwxrwxrwx    1 kirschh  user           65 Feb  8 13:59 bin -> 
> > > ../../../../../projects/bi/TextMining/Linux/stow/liontm-3.1.1/bin/
> > > lrwxrwxrwx    1 kirschh  user           70 Feb  8 13:59 htmldocs -> 
> > > ../../../../../projects/bi/TextMining/Linux/stow/liontm-3.1.1/htmldocs/
> > > drwxr-xr-x    2 kirschh  user         4096 Feb  8 13:59 lib/
> > 
> > It seems to me that there is an extra ".." in the previous links, maybe
> > because ~/tmp/ggg used to be one path level deeper ?
> > 
> > Stow tries to find if the link points into the stow repository; It will
> > not remove links that point elsewhere. So here I guess the problem is
> > that stow doen't detect that the extra ".." can be ignored since it goes
> > through /.
> 
> Fixed in CVS.

I now tried to dig deeper into the problem and found the error can
only be forced when

1) The shell's (in this case tcsh) $cwd is different from /bin/pwd,
i.e. when I cd to the stow-directory via a soft link.

2) Stowing is then done with stow-1.3.

I guess this is related to the "Removed buggy fastcwd" comment in the
release notes to 1.3.3. As you noted in your previous mail, it looked
like I had moved ~/tmp/ggg one level up, which was not the
case. Seemingly, stow-1.3 puts one ".." to much into the path. This
does not result in broken links if the correct number of ".." leads
anyway already through "/" (at least on Linux).

Consequently, it makes sense to mimic this behaviour in stow. However,
my original problem was caused by stowing with 1.3, contrary to what I
thought and reported. Sorry for the inconvenience.

  And thanks for your help,
  Harald.

-- 
----------------+----------------------------------------------------
Harald Kirsch   | address@hidden
LION bioscience | +49 6221 4038 172