I have created new version of the ebuild, that compiles versions >= 1.24 because the author of this small webserver changed the package (no he uses tarball instead of single .c file). Reproducible: Always Steps to Reproduce: 1. 2. 3. I am including patches for ebuild, xinetd config, init.d config and the new configuration file (shttpd now uses /etc/shttpd/shttpd.conf file). Including also already-patched versions for those who do not like patches :-)
Its a www-servers/shttpd.
Created attachment 61831 [details, diff] ebuild 1.21 --> 1.25 diff
Created attachment 61832 [details, diff] files/shttpd.conf patch to v1.25
Created attachment 61833 [details, diff] files/shttpd.confd patch to v1.25 confd (not conf) - sorry, because there is also "conf" file
Created attachment 61834 [details, diff] files/shttpd.xinetd patch to v1.25
Created attachment 61835 [details] shttpd now uses config file, this is gentoo-ready config files/shttpd.conf
Created attachment 61836 [details] Patched version 1.25 (if you do not like patch :-)
Created attachment 61837 [details] Patched version 1.25 (if you do not like patch :-)
Created attachment 61838 [details] Patched version 1.25 (if you do not like patch :-)
I am not sure about braking lines in ebuilds with "\". It works but there are much useless whitespace - please fix it. opts="-DCONFIG=\"/etc/shttpd/shttpd.conf\" \ -DWITH_SSL ${PN}.c -o ${PN} -lcrypto -lssl"
Please use the unified diff format (diff -u) in the future. No need to post patched versions, as just the diffs will do. This is on my todo list for tonight at work so it should be done in the morning.
oops and I forgot to mention. Always use text/plain for text files (patch is fine for patches), otherwise it's not possible to view it in the browser.
Did you try testing it at all? There seems to be something b0rked with the config file code. Unless I remove the config file, it dies every time with: ].Each line in config file must be in format '<var> <value>' It does this regardless of config (yours or the one distributed by uptstream). I don't have the time now to look into it, but needless to say until I get/write a patch or he releases a new version that fixes it, it's not going into portage.
Got the bug! The conf file was created under Win32 with Windows-like linefeeds. Please fix it using Vim or recode, thank you. Will notice the author.
In CVS. Thanks Lukas.