Erich, Sure, I have no problem with backporting this when necessary. Like I said, buildtool will makes this a matter of minutes. In the case we change to a new uClibc version, I (we) will keep the previous crosscompiler around.
I agree that seperating binaries from scripts eliminates this to some extend (you still have to do a backport when haserl or pwcrypt changes because of a security problem or so). But seperating binaries would mean yet another dependency and again an extra package. I disagree about mini-httpd to be part of webconf, both haserl and pwcrypt are bound to webconf, you don't have an alternative. But you can use an other httpd if you like (f.e. the ssl linked mhttpds or even apache ;-)) Eric >Erich, > >Webconf is ported to buildtool, so making packages for a new uClibc >version would only mean run buildtool to automatically recompile and >create the packages. > > Sure, but will you backport? Separating binaries from scripts eliminates this. Else one could argue that mini-httpd is part of webconf too. cheers Erich ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
