Mail Archives: cygwin/2005/02/11/14:40:25
On Fri, 11 Feb 2005, David Rayner wrote:
> Peter
Hi David,
(I've cc: the list as this is relevent).
> An updated version of zsh (zsh-4.2.4-1) has been released and should be
> >at a mirror near you real soon.
> >
> Peter (I don't seem to be able to post today)
>
> On my Pc
> echo $ZSH_VERSION
> always revealed
> 4.2.0
>
> Then I remembered I'd had this b4, I then used W-Explorer to copy
> /usr/bin/zsh-4.2.4.exe to zsh.exe
I recall someone else reporting this before (with 4.0.7?), and I think it
had to do with symlinks, or perhaps breaking the original file hardlink.
You see, zsh.exe is a hardlink to zsh-X.Y.Z.exe. If you list the package
contents (via tar -tjvf) you'll see this:
hrwxr-xr-x doctor/None 0 2005-02-08 07:53:41 usr/bin/zsh.exe link to usr/bin/zsh-4.2.4.exe
Now, it's possible to create a symlink for an existing file. Please
check that you don't have a symlink/short-cut for zsh (zsh.exe.lnk or
zsh.lnk). I'd recommend checking this from a DOS Prompt so nothing is
obscured. It's also possible that setup, when it removed the old
package, discovered that zsh.exe was no longer a hardlink and didn't
remove it, but that's just speculation on my part (haven't explored
setup's uninstall package logic lately :), but I seem to recall that if
you remove the package, then manually remove zsh.exe, zsh-X.Y.Z.exe and
libzsh-X.Y.Z.dll (if they are left over) that subsequent
install/uninstalls work as intended. Are you using NTFS or FAT for the
filesystem? As for my self, I've never been able to reproduce this, and
once the manual intervention is done it seems to solve the problem for
others.
> Now I get
> >echo $ZSH_VERSION
> 4.2.4
>
> >ll zsh*
> -rwxrwxrwx+ 1 davidr Users 7168 Feb 8 15:53 zsh-4.2.4.exe
> -rwxrwxrwx+ 1 davidr None 7168 Feb 8 15:53 zsh.exe
> -rwxrwxrwx+ 1 davidr Users 6656 Apr 9 2004 zshold.exe
>
> I think that there's also some issue where, when zsh upgrades you don't
> necessarily get any updated /etc/z* files, ie you
> have to manually copy them across?!?
This has been addressed. As of 4.2.3 the package does proper
instatiation and removal of /etc/zprofile, using the same method that the
base-files package uses (via preremove and postinstall scripts which test
for changes in the profile before removing). Note that when upgrading
from a pre-4.2.3 version of zsh you will need to manually remove
/etc/zprofile before installing a 4.2.3 or later version to properly sync
things. This was vaguely alluded to in the announcement for 4.2.3.
I also recommend that if you have any customizations you'd like to keep
for shell startup that you either put them into one of the other global
startup scripts (/etc/{zshenv,zshrc,zlogin}) or put them into your
per-user startup scripts (~/.{zshenv,zprofile,zshrc,zlogin}) instead of
modifying /etc/zprofile.
--
Peter A. Castro <doctor AT fruitbat DOT org> or <Peter DOT Castro AT oracle DOT com>
"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/
- Raw text -