ecopy www-servers/lighttpd to add www-servers/lighttpd-1.4.19-r2 ebuild into portage overlay. and then copy all the subdirectories of files/ from the official portage ( or use the patched ecopy from bug #223295 ). The emerging will fail because the ebuild install all the libraries to the hardcoded path /usr/lib/lighttpd/* . A patch to the ebuild which will be uploaded laterly can fix this issue. Reproducible: Always
Created attachment 154037 [details, diff] patch to correct lib path
How do you start lighttpd? % lighttpd 2008-05-23 10:06:55: (server.c.548) No configuration available. Try using -f option. Should there be a config file available somewhere or is it user generated?
(In reply to comment #2) > How do you start lighttpd? lighttpd needs a configure file to start up. The official portage will install an example configure file at /etc/lighttpd/lighttpd.conf, and /etc/init.d/lighttpd uses it to start the service up. Unfortunately, for gentoo prefix, init.d stuffs do not work, and the installed example configure file ($HOME/Gentoo/etc/lighttpd/lighttpd.conf) does not work out of box, either. You should make some modification to the lighttpd.conf to make it work, including the path and port number, etc.
(In reply to comment #3) > lighttpd needs a configure file to start up. The official portage will install > an example configure file at /etc/lighttpd/lighttpd.conf, and > /etc/init.d/lighttpd uses it to start the service up. I didn't see the conf file in etc/lighttpd. If it is there in gentoo-x86, we should have it there in prefix. I could be wrong though, because I am not at my prefix to double check. > Unfortunately, for gentoo prefix, init.d stuffs do not work, and the installed > example configure file ($HOME/Gentoo/etc/lighttpd/lighttpd.conf) does not work > out of box, either. You should make some modification to the lighttpd.conf to > make it work, including the path and port number, etc. Can we patch these changes in?
(In reply to comment #4) > (In reply to comment #3) > > lighttpd needs a configure file to start up. The official portage will install > > an example configure file at /etc/lighttpd/lighttpd.conf, and > > /etc/init.d/lighttpd uses it to start the service up. > > I didn't see the conf file in etc/lighttpd. If it is there in gentoo-x86, we > should have it there in prefix. I could be wrong though, because I am not at my > prefix to double check. It is in $EPREFIX/etc/lighttpd/, please check again. :) > > Unfortunately, for gentoo prefix, init.d stuffs do not work, and the installed > > example configure file ($HOME/Gentoo/etc/lighttpd/lighttpd.conf) does not work > > out of box, either. You should make some modification to the lighttpd.conf to > > make it work, including the path and port number, etc. > > Can we patch these changes in? Yes we can, we can fix all the paths to prefix offset and change the listen port to a higher number (e.g. 8080) because we do not use root previledge. However, I doubt if it is nessicery as the lighttpd.conf installed by portage is mainly used by the init.d service, which is unusable for now.
(In reply to comment #5) > It is in $EPREFIX/etc/lighttpd/, please check again. :) I didn't have $FILESDIR/conf in my overlay, too bad the ebuild didn't die() =/ > Yes we can, we can fix all the paths to prefix offset and change the listen > port to a higher number (e.g. 8080) because we do not use root previledge. > However, I doubt if it is nessicery as the lighttpd.conf installed by portage > is mainly used by the init.d service, which is unusable for now. Agreed. We decided to add and mask this because a) we don't want to support a config file patch and b) users that install this should know how to configure it. Could you please try to emerge it from what I committed (ie. move it out of your local overlay after you synced and reopen this bug if I messed something up ;) Thanks!
r22620
