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. > 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. Now freenet/ contains .deb package built from -official, and freenet-staging/ contains one built from -staging. > 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. 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? Best regards, MH -- Masayuki Hatta Graduate School of Economics, The University of Tokyo Manufacturing Management Reserch Center, The University of Tokyo mhatta at mhatta.org / mhatta at grad.e.u-tokyo.ac.jp mhatta at gnu.org / mhatta at debian.org / mhatta at opensource.jp
