This is my first attempt at a webapp.eclass ebuild and I wanted to get the herd's approval before committing it to portage. Another reserve I have is that only people who have the bandwidth should install this package; should something that could potentially bring home servers to their knees be placed into portage (even with all the warnings)?
Created attachment 39021 [details] net-p2p/gwebcache-1.0.0.ebuild
Created attachment 39022 [details] /files/reconfig
Jon, Thanks for showing it to us first. Looks good, here are some comments as you requested: - I'd ${P} in SRC_URI :) - don't use vhosts in IUSE, the eclass will handle it for you - I'd give a more informative warning in preinst. Also, don't sleep unless you want Mr_Bones_ to hunt you down - don't rm things in src_install, same reason :). just do a more selective cp -R - I'd drop pkg_postinst and move the instructions into webapp postinstall instructions (see man webapp.eclass) - the reconfig hook should clean up after itself, so throw in a quick rm when called with "clean". Looks good otherwise, great work!
Also, I'd chmod +x in the ebuild as opposed to the reconfig hook.
I've decided not to add this to portage- I think there's a faster gnutella web caching client anyways.
