On Wed, 7 Apr 2004, Christopher Faylor wrote: > On Wed, Apr 07, 2004 at 06:40:57PM -0700, Peter A. Castro wrote: > >*grumble* Hmm... I suspect this is really a Setup issue. The binary > >is stored in the tar as a hardlink to the versioned name. If you > >manually unpack it, with tar, it does the right thing. On an NTFS > >volume, it makes it a hardlink to the real file (ie: link count = 2). > >On a FAT volume, it duplicates the file's contents (ie: link count = > >1). It appears setup isn't quite handling it correctly for your > >configuration. We'd have to get detailed info about your config. Are > >you using the latest setup.exe, btw? If not, try a snap-shot first. > >It's as simple a un-installing and re-install zsh to test. > > Again, setup.exe does not understand hard links. So if you use a hard > link in your tar file, you will not get a hard link when setup.exe > installs it.
I know you've said that, but, that doesn't account for what I see when I install zsh, via setup. It does duplicate the file: E:\cygwin\bin>ls -al zs* -rwxrwxrwx 1 Administ Administ 6656 Apr 3 23:12 zsh-4.2.0.exe -rwxrwxrwx 1 Administ Administ 6656 Apr 7 19:41 zsh.exe This is from a freshly installed zsh after I de-installed and manually removed all traces for zsh from the system. No, I haven't looked into how setup is doing this, and no, I can't explain why it works for me, but not zapper. I'm hoping getting some info from zzapper's test will shed light on the subject. > cgf -- Peter A. Castro <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]> "Cats are just autistic Dogs" -- Dr. Tony Attwood -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/