Hi Jon I think that your proposal is a great idea. Let's me explain my opinion. I have the impression that the acceptance of the CDE desktop is impacted by it not available in major distribution. There are some work, but they are not including it. I have try to resurrect it in fedora/openSUSE for ARM/x86/x64.
https://build.opensuse.org/package/show/home:joserubiovidales/cdesktopenv So far, there are progress, the work is in progress and I will submit a pull request from by sf branch when i fill more confident. . I'm pretty sure that some of the patches will be really useful, in fact bringing the work of the different branches to master will increase the adoptability of the CDE and avoid duplicated efforts . Related to your questions: 4) I'm not aware of them, i can add to my fork and test them. Where are they 5) I vote +1 for the dtksh. I'm patching and I will send a merge request. I have sent 4 merge request. Two of them are necessary to compile for ARM/x86/x86-64 in Fedora and Suse. If you are going a merge, the two merge request necessary to compile and execute the CDE in the raspberry pi and fedora/suse are. * link-linux-libtcl https://sourceforge.net/p/cdesktopenv/code/merge-requests/7/ * linux_aarch64 https://sourceforge.net/p/cdesktopenv/code/merge-requests/6/ I dont' know the process you follow, but i can send in the format that best suit your workflow. Regards and thank you for the great effort jrv El jue., 12 sept. 2019 a las 7:11, Jon Trulson (<j...@radscan.com>) escribió: > > As has been pointed out in IRC, there are some security fixes in current > master. There are a variety of other fixes that have gone into master > as well since the last release. We are overdue, as usual, for a new > release. > > We could just do a version now based on current master, or we can wait a > bit to decide some of the issues described below first: > > > 1. Has any one tested the utf8-conversion branch yet? Should it be > merged into master yet? If not, then I will merge it to master after > release and let the bugs flow forth. > > 2. cde-next branch - should that be merged into master first? Peter? > I'm not sure what's current there ATM. > > 3. Are there any other patches that need to be sent in by the various > maintainers for the BSD's, Solarii, etc? > > 4. There were some patches (diffs actually) recently posted to the list > (Subject: "Some untested patches") - scroll support in dtterm etc. What > shall we do with those? I didn't have the time to break these up into > proper patches for review and test. > > Anyone want to turn them into a proper patch submission? > > > 5. There's also a fix for a fedora and opensuse bug in building ksh in > CDE: > https://sourceforge.net/p/cdesktopenv/discussion/general/thread/24d7511a39/ > > Someone want to test and make a patch? I'm sorry, I just don't have > time to go trawling through forum posts to assemble proper patches. > > Since the exploit does not currently work with our CDE (though the code > *is* definitely broken), I am more inclined to take a few weeks and > incorporate some of the fixes above (though not utf8-conversion if no > one else has really tested it yet.). > > Otherwise we can just create a release based on current master and > integrate the above stuff "later". > > > -- > Jon Trulson > > "Nothing unreal exists." > -- Kiri-kin-tha > > > _______________________________________________ > cdesktopenv-devel mailing list > cdesktopenv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel >
_______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
