Another, originally unrelated problem: an alternatives system. We already have conflicts: • /bin/sh: busybox (ash), mksh, bash(NOT!) • ed: busybox (ed), ed • vi: busybox (vi), nvi, vim
I'm intending on adding an rdate package. Now, busybox already has an rdate, which is a little smaller but doesn't do SNTP. (And I'm not going to add that to busybox, sorry.) We need something to resolve this. Maybe something like this: in mksh: FLAVOURS+=ash binsh, PROVIDES_ash=ash, PROVIDES_binsh=sh in busybox, add a few PROVIDES in rdate: PROVIDES=rdate etc. Then, the nfotiser must check for conflicting PROVIDES values and add an appropriate resolution mechanism. So far, so good. But how should that look to the user? At the moment, we have a hand-refined menu “Shells”, and other stuff isn't checked. How about a new menu named “Package Alternatives”, where you can select between the conflicting flavours? This proposal's bad side is: configuration of a package is not at one single place any more. Dependent configuration (e.g. the “ash options” that are only visible) gets harder (we can put the alternatives menu before the packages selection menu then). Ideas? bye, //mirabile -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
