SkunkWeb 3.4.0 is now out. The docs were being installed incorrectly in the previous ebuild, so I attach a corrected ebuild. Reproducible: Always Steps to Reproduce:
Created attachment 39401 [details] dev-python/skunkweb-3.4.0.ebuild
Created attachment 40125 [details, diff] diff against current skunkweb init file The skunkweb-init file in the current skunkweb ebuild depends on apache2. This is wrong, I believe, for 3 reasons: 1) skunkweb doesn't necessarily need apache at all, and there are use flags for apache1 and apache2, so it is inconsistent to hardcode apache2 in the init file; 2) apache2 will give 500 errors for any resources handled by skunkweb while skunkweb is off. Therefore, apache should always be started *after* skunkweb and turned off *before* skunkweb is turned off; 3) the init script supports a "configtest" option, which just tests to see if the configuration can be loaded without error, but I believe it would have the side effect of turning on apache! So for all these reasons I don't think adding apache2 as a depend is the best default, although it might be ok in some installations. The above patch simply removes the depend.
Sorry to nag, but I can't resist a little nudge -- I'm the developer of skunkweb, so I can vouch that this ebuild is OK to check in; in fact, I'd say it is stable (I'm using it in production on several servers) and 3.4b5 should really go away soon.
Thanks Jacob, added to CVS.
