On Sun, Mar 23, 2008 at 1:09 PM, Florent Daigni?re <nextgens at freenetproject.org> wrote: > > It's only an issue since Freenet gets updates so often. When it's > > stabilized you can make a more standard package. > > When will it be stabilized? Will it ever be?
The various package systems assume some stability in the software releases. Until then (say, at the "official" 0.7 release), Freenet is not a good match for Apt or RPM. Not saying the packages can't be built -- or even kept up-to-date -- just that it won't be added to the stable repositories. > What about ubuntu and other distros ? We may need to set up a package repository for Freenet on the freenetproject.org site. Have the update script (under Debian, Ubuntu, &c.) just run an apt-update (or whatever the command line is) to refresh the view of the freenetproject.org repository and update only those packages. An alternative could be to give the freenet daemon permission to update itself, and decouple the package version from the freenet release version. That will require update-over-mandatory, or giving the daemon the smarts to connect to freenetproject.org when needed. --Joel
