Hi Enrico, On Fri, 2010-10-01 at 22:05 +0200, Enrico Weigelt wrote: > * davidMbrooke <dmb.leaf-de...@ntlworld.com> schrieb: > > > are other priorities at the moment - like getting a robust 4.x release > > based on a 2.6 kernel, Shorewall 4.4 etc. accompanied by accurate and > > useful documentation. > > What has yet to be done for that ?
1. There are still some 3.x packages that do not build successfully on 4.x / with GCC 4.x. Andrew, kp and I are working away at those but there are more to fix (or decide to drop). 2. As you noted in a separate mail we have many packages based on old upstream versions. In some cases we "held back" the version to keep the disk image size small or for compatibility with the 2.4 kernel. Some analysis would be useful, to understand what upstream version we are using now, what the latest available upstream version is and whether we should plan to upgrade. Then there is the task of actually changing to new versions... 3. The documentation needs a lot of work. We have just started using MediaWiki but this is rather experimental at the moment and the User Guide in particular is not well developed. I had hoped to spend more time on that but recently I have been fixing code instead... There is some excellent material in the manuals for the older releases which needs reviewing and updating to match the new system. 4. IMHO we could do better at tracking problems / enhancement requests and assigning ownership for fixes. Right now there are only a few active developers and this mailing list is our main communication tool. It works OK, most of the time, but if we have more developers it will be more difficult and once we get to a formal Alpha / Beta test stage I think there will be more problems to keep track of. Perhaps someone could look into Trac or similar for this? 5. There are enhancements that could be made. For example: - There is no "dependency" handling when installing packages. It would be ideal if a package automatically installed all of its pre-requisite packages (if not already installed). Much of the framework is already in place within the "apkg" sub-system. - We would like to be able to boot Bering-uClibc 4.x over the network from a PXE / TFTP server but there is no support for that in the boot script at the moment. I think I will stop there since I'm sure you get the idea. :-) davidMbrooke ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel