The most recent freenet ebuild was from mid-February; the download for it no longer exists (and hasn't for months), and there have been many, many, many mandatory upgrades since then. Please remove it from the Portage tree as it is completely non-functional.
I think it's a bad idea. The old ebuild can be a reference to be used for newer versions. By the way, I did install it yesterday, and then ran "update-freenet" script, and it downloaded the latest version, that worked perfectly.
Well, I'm almost done with a new ebuild, anyway -- one that has to be updated very rarely but that re-emerging will update Freenet. Integrated seednode management, all kinds of other good stuff. Give me a little bit :)
ok, send the new ebuild to me, and i upload it. Thanks
Okay. This ebuild seems to work properly... it's a hack, a horrid hack, but it works. Every time it is installed, it grabs freenet-latest.jar, seednodes can be updated by ebuild freenet-0.4.ebuild config, and various other things. Good stuff. Also, I suggest that freenet-20020214.ebuild is either removed from CVS or masked, because no new installations can take place (that tarfile doesn't exist), and 20 million is larger that 0.4 :)
Created attachment 1636 [details] Spiffy new ebuild
Errr... hmm... it seems to update the seednodes even if you say "n"... :(
In the ebuild can't do ask to users, simply asume all to yes, or make a note to the finel of the ebuild with little instructions. And every files to download must put into SRC_URI if you can makes this changes great :)
"And every files to download must put into SRC_URI" I understand that's the convention, but with Freenet that won't work unless it gets mirrored. freenet-latest.jar is rebuilt every night from the sources and will have a different md5sum, if it were put in SRC_URI the ebuild would either a) have to be updated every single day at 00:35 GMT, or b) become inoperative because of forced node upgrades. Pointing it at the download tarballs (freenet-YYYYMMDD.tgz) doesn't work either, because they get deleted on a regular basis and the new ebuild schedule would just plain suck. It's non-standard (and probably 'illegal'), but it's really the only way to handle this problem effectively. Portage has no functionality to work with nightly builds. Besides, you have to be connected to the net to run Freenet anyway, so fetching it later in the merge isn't too bad. (Plus, when a notification comes that they have to upgrade, a new ebuild doesn't have to be released -- emerge freenet updates it automatically.) I'll modify the configure step and post the new ebuild shortly.
Created attachment 1671 [details] New spiffy new ebuild
sorry but we can't support files without digest file. I make a new ebuild for down the latest version of today, and put how to do for update it with freenet scripts thanks for all :)
Should I file an enhancement request for Portage to support nightly builds?
Nevermind, I already did. Bug #3989.
for the moment i bumped the ebuild, and you can use update-freenat for update it.
