Am Montag, 7. Juli 2014, 23:41:52 schrieb Erich Titl: > Hi Gents > > at 06.07.2014 15:02, Yves Blusseau wrote: > > Le 6 juil. 2014 à 14:39, Yves Blusseau <bluss...@zetam.org> a écrit : > >>> AFAIK unfortunately busybox-vi is not just a replacement, one needs to > >>> build it with a proper toolchain, and replace initrd… > >> > >> Can you explain ? > >> We can choose now which editor to use with the Platform_Editor buildtool > >> variable. If it is set to vi, busybox applet vi will be built. If the > >> value is different the applet will not be built.> > > After looking at sources i see what you mean. e3 can't be build on arm > > arch like rasberry-pi. What i proposed is to always build busybox vi > > applet so in any platform we will have an editor in initrd. Then the > > packager can choose which editor to use by default for the platform. > > > > What do you think about this ? > > Just my stupid 0.02xx > > The *x editor is either vi or emacs everything else is just a mock up. > If vi crashes ( and I don't think you want to port emacs to a embedded > system ) this is just a bunch of ***p. > > Before 4.x we had a pretty usable vi, with probably all the bugs one can > think of. The busybox stuff may be nice but is typically just a meager > replacement for the REAL thing. I am under the impression that for the > sake of new platforms and kernel features we are loosing some of the > stability and usability of former releases. > > Now just wish me to hell :-)
Not yet :) Erich, let me add - for security reasons as well and more important for new developers joining. In the last days of 3.x the former team members had vanished for various reasons, and beginning with 4.x new developers like Andrew, David and Yves jumped in and did a lot work to improve LEAF Bering-uClibc - buildtool/toolchain improvements, a major step towards a decent documentation in the wiki, a nice new logo, moving to git... - just to mention something else they provided, than the changes you "dislike" :) Without their work LEAF Bering-uClibc would have ceased to exist a few years ago. I think some difficulties to choose the proper vi are a good tradeoff. If we don't send you to hell, what about libreswan/freeswan as openswan replacement, which failed to compile for 5.x? I remember you did some work. but had no time to finish. Maybe leaf-devel can help? kp ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
