On Thursday 27 August 2009 14:20:39 Matthew Toseland wrote: > sashee's web-pushing branch should significantly improve Freenet's > responsiveness and usability, by making extensive use of web pushing, for > various generated pages, for inline images on a freesite, for messages etc. > > Currently, javascript is generated by GWT and checked in. ant distclean will > wipe this javascript, and if you have gwt-dev-linux.jar and gwt-user.jar in > lib/, it will be regenerated using GWT. We don't actually use any native > code, so this will hopefully work even on Windows. > > The problem is that GWT is rather difficult to build from source. It depends > on a load of native code, and a pile of third party libraries. Most of these > are provided in jar form. *Some* of them have source zip's provided, but in > terms of trust it would be better to get them from the source anyway. > > Clearly this is a problem that any linux distributor would have to deal with, > but we are years away from the point at which we can hand over these problems > to them. So how important is it to have a clean build path? I have explained > this in the README.clean-build for the web-pushing branch. Is it acceptable > to simply say if you want to rebuild the javascript, put gwt-dev-linux.jar > and gwt-user.jar in lib/ ? > > Related bug: > https://bugs.freenetproject.org/view.php?id=3448 > In the Freereader plugin, similar issues are resolved by downloading an official, versioned, checksummed binary, if necessary extracting jars from it, and adding a README.clean-build for distributors. This is probably the best option given the considerably difficulty in rebuilding not only GWT but most significant java software...
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
