Am Sonntag, 6. Juli 2014, 15:25:42 schrieb Yves Blusseau: > Le 6 juil. 2014 à 15:12, kp kirchdoerfer <kap...@users.sourceforge.net> a écrit : > > 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. > > If we ALWAYS build busybox with the vi applet we don't need to build > separate initrd.
True, but it consumes some more kb, which arent't useful for most of the users. Keep in mind - if we want to support MIPS-based routers we need to be small as possible, usually they don't have a lot of RAM (32 to 64 MB AFAIK). On the other hand there are a other options if someone wants to use vi, and I guess most users who wants to use vi will either satisfied with the very small e3vi, or won't complain to install additional 500kb vor vim-tiny, and if someone has a real need for busybox-vi, there is still an option to build himself - I doubt this happen soon. > > 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? > > Yes, the packager choose a default editor (which will set the profile EDITOR > variable). The final user can then change the EDITOR variable value to use > another editor. Actually there only a vim-tiny version (550Ko), > I can make a full feature vim version (2Mo) for users like me that use vim > intensively and use an elvis/elvis-tiny for other users. The problem is > that actually the elvis-tiny (1.4-22 or 1.4-23) segfault on my platform. So > perhaps it's better to use a "true" version of elvis (not tiny) that is > more stable (but larger) ? What's the diference between elvis and your tiny version of vim? In size they aboth about 500kb - don't know about dependencies (according to your vim buildtool.cfg it requires ncurses and libelf, elvis ncurses). So if we can't fix elvis-tiny and build elvis instead, it might be enough choice to just provide a 500kb vim and forget about elvis, which you also siad to be not error-free. We may also update elvis-tiny with latest version as it seems to run on a geode based router and see whatever happens in the future. In short: e3vi elvis-tiny for those, whom it works elvis/vim-tiny (your decision) full vim should fit most, if not all, users. 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
