Am Sonntag, 6. Juli 2014, 15:02:54 schrieb Yves Blusseau: > 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 ?
I've been to slow sending my mail :) It will be an improvement, anyway it will require to build a seperate initrd version, since busybox is loaded with initrd, and IMHO it's too much to provide seperate versions of initrd just to change the editor. Coming back to the topic: I think if a user wants vi instead of e3ne, he can choose between e3vi, vim(- tiny? Are those seperate version?) and maybe we can even fix elvis-tiny to have something smaller than vim, but more useful than e3vi? So I believe the restriction regarding busybox-vi is not a big problem. 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
