Hi all,
Recently I was attempting to fix and old patch of mine that switches ksh's hash
for DtHash, our builtin substitution in order to import upstream ksh. I looked
at ksh's github and everything seems to have imploded there. AT&T have stepped
in and reverted all major commits since 2012, a number of community devs have
quit and the project seems to be at a complete standstill. The branches seems
to have split into a ksh2020 branch (new commits by contributors) and a ksh93v
branch (2012 with few additions). How should we proceed with importing a new
ksh? Personally, I think ksh2020 had the right idea (at least in terms of
moving away from the mamfile build system), we could probably take it, autotool
it and hard fork from there. I will probably continue to work on the patch
because using our internal tools will be a lot better than taking from an
extremely volatile upstream, but thats not for me to decide, your thoughts Jon?
Marcin your input would also be appreciated as well.
Thank you for your time,
-Chase
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
