On Friday 07 August 2009 19:02:45 Masayuki Hatta wrote: > Hi, thanks for comments. > > >>>>> In <4f9383510908070718q48b6f28esf3b13e83ba983499 at mail.gmail.com> > >>>>> Evan Daniel <evanbd at gmail.com> wrote: > > > 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].) > > I'll investigate it. Currently, /etc/init.d/fred (I think this is the > Debian standard way) does the same thing, so > > # /etc/init.d/fred start > # /etc/init.d/fred stop > # /etc/init.d/fred restart > > should work as expected.
Okay... We use the wrapper *mainly* for auto-update, but also for restarting the node when we need to restart it to apply a config option, and for getting stack dumps. And for reliability. None of these are essential if you are proposing to turn off auto-update - but then the node will only be updated with dist-upgrade. If you leave auto-update enabled, it may clash with debian updates to the binaries... so it's a problem you'll have to consider. Mandatory builds are fairly common because we are still working on the protocol, as evanbd explained. > > > 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.) > > Oh, I thought fred-official is sort of stable but out-of-date kind > stuff, but obviously not...I rebuilt my package using -official. Yes, I forgot to post the updates to stable (I only posted the tags, and didn't update master). Sorry. > > Now freenet/ contains .deb package built from -official, and > freenet-staging/ contains one built from -staging. Cool. > > > 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. > > I'll add some notes on it to the package description. > > > 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. I'm assuming we wouldn't qualify for debian-volatile? In any case the first thing is to get a good package and repository working. > > Hmm, I didn't know the freenet protocol is still in a state of flux. > I can upload packages to sid/experimental and make it never enter into > testing, but I think it would be better to distribute them from the > official Freenet site or such for a while. Could someone upload or > put a link to my package repositry? The best option would probably be for me to build the package with your scripts and maintain a repository on our hosting? We upload the new jars, the windows and generic installers etc during the release process at present, and both installers are visible on the website depending on your OS. If we have a good debian package we would want to provide a link to an official freenet repository in the linux installation instructions. Having said that, I'm not a debian package maintainer, I don't have time to track all the goings on in sid. We want this to work on ubuntu, so it would probably make sense to minimise the external dependancies; and we only need to keep up with lenny (and eventually the next one), and possibly the ubuntu packages. If you want to maintain your own repo for sid, we could link to it as an unofficial repository, and when you have changes to push you could let me know and I could update the scripts that build the official package. IMHO it would be an important step forward to have a good debian package and our own repository, thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20090807/ab46fd19/attachment.pgp>
