Ksh2020, I submitted a patch importing the ksh93v branch, but Jon said he 
wanted to do away with nmake entirely and import ksh2020. As he has push access 
and I don't, that's what I've been working on :)


Thank you for your time,
-Chase

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, November 25, 2019 3:19 PM, Marcin Cieslak <sa...@saper.info> wrote:

> On Mon, 25 Nov 2019, Chase via cdesktopenv-devel wrote:
>
> > So as I was upgrading our ksh, I have ran into a problem, hash.h, commonly 
> > found in libast, is no where to be found in the new sources, come to find 
> > out that they have removed the entire hash part of the library because it 
> > was "unused". The way I see it we have three paths going forward if we 
> > still want to use the latest and greatest ksh, from easiest to hardest:
> > 1.) Ask upstream to revert their patch removing the code
> > 2.) Readd the code and maintain it ourselves (I think this should only be 
> > done if #1 fails)
> > 3.) Refactor our code not to use their hash code
> > I lean towards #1, but I thought I'd consult the group before I did 
> > anything.
>
> o
> Hi Chase,
>
> do you meaning as you were upgrading to the 2020 neo-ksh version or ksh93v?
> I had a look at ksh93v build system this weekend and with few improvements
> I think it could be pushed to CDE as is (without a much promised solution
> with a shared library :))
>
> Marcin




_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel

Reply via email to