On 3/30/09, James C. McPherson <james.mcpher...@sun.com> wrote: > On Fri, 27 Mar 2009 20:16:07 +0100 > Roland Mainz <roland.ma...@nrubsig.org> wrote: > > > "Mark J. Nelson" wrote: > > > > > > Gah. > > > > > > I guess my dirty little secret is out: I'm an OpenSolaris user, on all > > > of my systems (SunRay server and laptop.) > > > > > > Anyway, as of my webrev changes earlier today, the onnv version of > > > webrev will only work with ksh93. This works on OpenSolaris systems, > > > where /usr/bin/ksh is ksh93. It breaks on Solaris Nevada systems, where > > > /usr/bin/ksh is ksh88. > > > > > > As of my followup integration (which just completed), the #! line is > > > correct, and SNV and OpenSolaris users will continue to function. The > > > tools will be propagated in the next 30-60 minutes. > > > > > > In the mean time, you may use "/path/to/ksh93 /path/to/webrev" to get > > > the correct behavior. > > > > > > My apologies for not catching this in my testing. > > > > Erm... why is this a "flag day" ? OS/Net has ksh93 since Solaris 11/B72 > > and right now SXCE won't even boot without /usr/bin/ksh93 (don't worry, > > ksh93 is (like ksh88) delivered via the "SUNWcsu" package and therefore > > available on all systems). > > > > It's a flag day because there are lots of people who work on > Solaris 10 backports who prefer to use the onnv version of > webrev(1) - and if they run the onnv version on an s10 system > then they'll have problems.
Why doesn't Sun backport ksh93 to Solaris 10? Holger _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
