Re: xlaunch small glitch

2015-03-03 Thread Warren Young
On Feb 28, 2015, at 8:34 AM, cyg Simple wrote: > > From: Corinna Vinschen >> >> So now we would have the sysname >> >> CYGWIN_NT-10.0-WOW64 > > How about a change to something like CYGWIN_NT-W32-10.0 and > CYGWIN_NT-W64-10.0 instead? That’s a bigger change than the one already done, so more

Re: xlaunch small glitch

2015-02-28 Thread Jon TURNEY
On 28/02/2015 00:15, Denis Excoffier wrote: In the last xlaunch package, the etc/postinstall/xlaunch.sh reads: % cat /etc/postinstall/xlaunch.sh.done # add a start menu shortcut case $(uname -s) in *-WOW64) wow64=" (32-bit)" ;; esac /usr/bin/mkdir -p "$(/usr/bin/cygpath $CYGWINFORALL -P)/Cygwin-

RE: xlaunch small glitch

2015-02-28 Thread cyg Simple
From: Corinna Vinschen > > Just for your information: This change from WOW64 to WOW in the uname > sysname output was forced on us to account for the excessive version bump in > Windows 10. > > Rather than bumping the kernel version to 6.4, which would have been the right > thing to do, the mark

Re: xlaunch small glitch

2015-02-28 Thread Corinna Vinschen
On Feb 28 01:15, Denis Excoffier wrote: > Hi, > > In the last xlaunch package, the etc/postinstall/xlaunch.sh reads: > > % cat /etc/postinstall/xlaunch.sh.done > # add a start menu shortcut > case $(uname -s) in *-WOW64) wow64=" (32-bit)" ;; esac > /usr/bin/mkdir -p "$(/usr/bin/cygpath $CYGWINFOR