Hi, 2010/8/3 Thomas Sachau <tommy at gentoo.org>: > Am 02.08.2010 07:19, schrieb Masayuki Hatta:
>> 1. Currently, so-called headless build (without setting DISPLAY) >> fails. ?This is a serious problem since the automated build daemon is >> quite common not only in Debian but also other distros in general >> these days. ?Seems the culprit is AWT, but I can't figure out why. ?I >> attached the log from failed build session using by pbuilder[2]. > > Do you really just want to use some installer and run that and call that a > "debian package"? > Shouldnt you instead build everything, which means freenet.jar on one side > and every package in > freenet-ext.jar from source and create your .deb files for them, which are > then used? I'm not sure what you mean. Do you mean I should NOT build Freenet from source?(currently it does, at least for freenet.jar). Anywise, just shipping pre-built binaries (.jar's with installer or whatever) from the upstream is not an option for me, at least for packages in Debian "main". Generally speaking, Free Software such as Freenet is supposed to be built from source cleanly and without much hassle. If it doesn't, then it means it has a serious bug. >> 2. The build system around GWT is not so sophisticated, IMHO. ?Seems >> it requires to put some needed .jar's into generator/js/lib, ?and the >> file name in build.xml is wrong(GWT.lib.dev should be >> gwt-dev-linux.jar on GNU/Linux), etc. > > At least currently, you dont need the GWT part to get a running node. And > since i dont know of any > working package on any distro to completly build GWT from source, i dont see > it happen in the near > future. > > I also hope, that GWT wont become required until there are at least working > instructions to build > GWT completly from source without the help of precompiled libs or jars. Debian/Ubuntu has GWT .debs in main, which means complete source code is available somewhere. Yeah, they seem to require to do some tricky stuff to build, but as far as I could see GWT can be built from source completely and in fact it currently does. Also, GWT now seems to be a somewhat requirement for building Freenet. If GWT .jar's are not present in generator/js/lib then build.xml tries to download gwt-dev.jar from http://localhost/(see line 84). I guess this is a bug. >> 3. The home-brew build of freenet-ext.jar still fails. ?Is there >> anyone who could actually do that? > > See above. I have splitted it completly into pieces and do build them from > source, so it is at least > possible and working. > > However, be aware, that freenet does create broken archives for inserted > directories with >=ant-core-1.8 Nice, I'll investigate it. >> 4. Still not using Java wrapper(thus automated update doesn't work). >> I did begin to work on this a year ago, but I need to refresh my >> memory now...also, as toad puts it, it can be debatable whether it >> should be allowed to modify the installed binary(in this case >> /usr/share/java/freenet-cvs-snapshot.jar or such) by means other than >> installing updated .deb., at least FHS-wise. > > Using the java wrapper should not be a problem, if it is properly packaged. > But freenet should not > autoupdate itself, instead, it should be updated via package manager as any > other packaged program. Agreed. Java wrapper seems to be difficult to use properly, anyway. Best regards, MH -- Masayuki Hatta <mhatta at gmail.com>
