On Fri, Aug 7, 2009 at 9:21 AM, Masayuki Hatta<mhatta at mhatta.org> wrote: > Hi everyone, > > I couldn't find any up-to-date Freenet .deb package on the Net, so I > made up one by myself. ?Currently it's based on fred-staging, Git > snapshot of freenet. ?I built/tested it on Debian sid running on an > IA32 machine, but you can re-build it on 64-bit machines or the latest > Ubuntu without much hassle. > > You may apt-get it from: > > deb http://people.debian.org/~mhatta/debian/freenet ./ > deb-src http://people.debian.org/~mhatta/debian/freenet ./ > > I tried to make it comply with the Debian policy as much as possible, > and seems it works nicely AFAIK, but some issues remain: > > 1. fred in this package doesn't use wrapper -- so you'll see some > warnings. ?fred is directly controlled by Debian's > start-stop-daemon(and I think it works well). ?The main reason I don't > use wrapper is, quite simply, I don't know how to use it ;-< Helps are > welcome. ?See /etc/init.d/fred for detail. > > 2. The build system can build freenet-ext.jar, but the self-build > version of freenet-ext.jar doesn't work somehow(causes hang up at > daemon startup). ?Is there any special way to build it? ?Currently the > build of freenet-ext.jar is disabled in debian/rules, so the shipped > version of freenet-ext.jar will be downloaded from the official > Freenet website everytime you build this package. > > When these issues are fixed, I'm planning to upload this to the > official Debian archive for inclusion. ?Comments, suggestions or > criticism will be appreciated.
Very cool (haven't tested it yet). For detailed instructions on using the wrapper, I suggest reading the run.sh file. (On a normal *nix Freenet install, one controls the node by ./run.sh [start|stop|restart].) In general, you should probably track fred-official rather than fred-staging. The official branch is where the official builds come from, and they're plenty frequent enough. That's where the builds for the auto-update come from, for example. (Speaking of which, you may want to ensure that's disabled, if the package manager is expecting to handle such things.) IIRC, the freenet-ext.jar issue is a known problem; I don't know what the state of it is, though. You may want to make sure the build claims an appropriate amount of disk usage, if you haven't already: on first startup, Freenet will normally create a datastore of at least 256 MiB. This is not accounted for in the sizes of the files shipped in the package. Inclusion into the official Debain archive would be nice, but is problematic. The main reason is the update frequency. Mandatory builds are not uncommon (1-2 per month, perhaps) on Freenet for a variety of reasons; if you're not running the latest mandatory build, you can't talk to the network. That poses problems for Debian's update frequency, though it might be possible to have something that was perpetually in unstable with no intention of migrating to stable. I don't know enough about the policies surrounding testing to comment on that. HTH, Evan Daniel
