Am Montag, 11. Juli 2011, 21:55:39 schrieb Erich Titl: Hi Erich; a valid, although difficult question...
> <topic off> > I am questioning a number of package decisions organically grown from > the past. > > - dropbear vs. sshd suite (dropbear does not appear to support sftpd) > - dnsmasq vs. djbdns suite and dhcp > - pump vs. isc-dhcp client vs. dhcpcd > there must be more of those... openvpn vs openswan? :)) > IMHO it would be beneficial to just support one single package to do a > certain thing. > If someone wants to build a package offering the same functionality, I > would suggest to fork off a branch and see which one succeeds out in the > wild. The main branch may loose :-( > > We could/should concentrate our forces on those packages, this makes the > distribution more lean and will enable us to include more packages for > other uses. It will also greatly improve the build of user interfaces. > </topic off> The are various reasons to build a package that "doubles" the features an existing package provides - e.g. fits better into an embedded environment (dropbear), adds features (dhcp/pump), easier maintenance and configuration (dnsmasq) or by user request and all of the above (openvpn - I know this example is questionable). The main factor is, is there anyone who wants to support and maintain the package. If so, I can live with the fact providing different packages for a similar task. It's also difficult to remove a package or feature once it's added - djb software has been added during the Bering times years ago, the Bering-uClibc team managed to provide it during transition, and to my surprise there are still users out there using it, providing bug reports and eventually fixes, ven it hasn't seen updates for years. But then, if it's possible to get it working, it's a plus for LEAF. IMHO (re)building a package which is still used does not mean that we are responsible to solve each and every pb - once a security patch does not compile any longer opens up the issue to the community. And if we talk about a webinterface you (as everyone else) is free to concentrate on the package you are most keen to do. I do not think that restrictions will work. ipsec has been outphased long ago in my setups, you still rely on it and provide the work needed to get it updated to 4.0 series, and that's good! If there are continous improvements for a give package, others will go away over time (like I expect for pump), but I think that's an evolutionary process (lack of updates, lack of supporters, webiinterface for isc-dhcp...), no need to make strict decision yet, IMHO. kp ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
