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 :-) cheers Erich ------------------------------------------------------------------------------ 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
