On Nov 16, 2019, at 11:10, joerg van den hoff wrote: > On 16.11.19 13:14, MacPorts wrote: >> #59699: ksh93: Update to latest version >> ---------------------+------------------------ >> Reporter: jghub | Owner: ryandesign >> Type: update | Status: closed >> Priority: Normal | Milestone: >> Component: ports | Version: 2.6.2 >> Resolution: fixed | Keywords: >> Port: ksh93 | >> ---------------------+------------------------ >> Comment (by ryandesign): >> Thanks for reminding me to update this port. >> Since there has been a new stable release since the last time I looked at >> this port—the first stable release since ksh93—I took the opportunity to >> rename the port from ksh93 to ksh and to update it to the new stable >> version. > > understood. this ksh reports > > Version A 2020.0.0 > > as its version string ($KSH_VERSION) > >> If you'd rather use a newer development version, I added a ksh-devel port >> you can use instead. > > this is really great and appreciated since ksh seems under quite heavy > refactoring/tidy up efforts so changes should be coming. this ksh-devel > reports > > 2020.0.0-beta1 > > as its version string. I am not sure how this string/variable (KSH_VERSION) > acquires its value but presumably during the build process? if so, I believe > the value actually should be > > Version A 2020.0.0-beta1 > > i.e. include the leading `Version A ' which seems the only invariant > identifier across versions to verify that the currently running shell > actually is a ksh93. the previous ksh93 package (which I believe was this > 'devel' version actually was reporting the version in the canonical way. > > question: is this a macports issue or are you not in control of the version > string? I would then contact the ksh93 maintainers. I can confirm that difference in the KSH_VERSION, but I'm not doing anything differently when building the two versions, so it's an upstream change.
