Summary: | lighttpd-1.1.4.ebuild (New Package) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Boris <1723542c42148b2fe4af9f7ad1e382b30d4b7fd7> |
Component: | New packages | Assignee: | Gentoo Web Application Packages Maintainers <web-apps> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | enhancement | CC: | 1723542c42148b2fe4af9f7ad1e382b30d4b7fd7 |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://jan.kneschke.de/projects/lighttpd | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
lighttpd-1.1.4.ebuild
lighttpd-1.1.4-gentoo.diff lighttpd.initd lighttpd-1.1.8.patch lighttpd-1.1.8.patch lighttpd.initd.patch lighttpd.initd.patch |
Description
Boris
2004-04-05 02:18:13 UTC
Created attachment 28723 [details]
lighttpd-1.1.4.ebuild
Created attachment 28724 [details]
lighttpd-1.1.4-gentoo.diff
Created attachment 28725 [details]
lighttpd.initd
Package: net-www/lighttpd-1.1.8 I've committed your ebuild; it should appear on an rsync mirror near you in about an hour. Could you test it please, and let me know whether it works for you? Thanks, Stu Doh - forgot to change the status of this bug. Created attachment 29923 [details, diff]
lighttpd-1.1.8.patch
The new ebuild did not work for me.
The major problem is that you changed the log-dir/files in the config but
forgot to do it in the ebuild.
The ebuild creates the logdir and sets it writeable for the user lighttpd. It
did this for the logdir I defined, so the server failed to start complaining
about the missing logfile/writeaccess.
I changed that in the attached patch.
Second you put the log-files into /var/logs/lighttpd. I corrected this to
/var/log/lighttpd were all other logs are located. I think this should be the
right place (also according to the FHS).
Last I added an information for those users that want to use fast-cgi and php
with this server, because this configuration is not trivial. (I am going to
write an fast-cgi ebuild and will add an php-useflag in the future, perhaps for
the next release, perhaps earlyer. But I am not shure how to implement this
yet)
I also added the mysql and ssl useflags to the (R)DEPEND. I had totally
forgotten this last time.
With the applied patch the package compiles fine and the server starts
"out-of-the-box" with no problems.
Thank you for checking this. I've applied the patch, and committed the changes to Portage once more. I've changed the ebuild, so that modules are installed into /usr/lib/lighttpd, rather than into /usr/lib directly. Best regards, Stu Created attachment 29941 [details, diff]
lighttpd-1.1.8.patch
The ebuild had a strange behavior when installing the files to /usr/sbin and
/usr/share/man which were installed to ${D} because of your change to the
einstall.
I created a patch to apply againgst the current cvs to workaround this. by
moving the files from ${D}/var/tmp/portage/... to ${D}/usr manually. I am going
to have a closer look at this this evening.
I also added 2 echos to clearly seperate the infolines from the rest of the
output.
With the patch the ebuild works fine.
Okay - the problem seems to be that einstall tries to be too clever for its own good. I've replaced it with the traditional 'make DESTDIR=${D} install', and this seems to have fixed it. Best regards, Stu Ok, this version runs fine here. Great work. Greetings Boris Sorry it took so long, and thanks for the great feedback. Many thanks, Stu Created attachment 30063 [details, diff]
lighttpd.initd.patch
I found a little mistake in the init-script:
RET was set to the return-value of ebegin and not the one of kill.
I corrected that in the submitted patch.
Hope this is the last comment I write on version 1.1.8 and everything is fine
now. ;-)
Greetings Boris
Created attachment 30070 [details, diff]
lighttpd.initd.patch
Thanks. I've committed your patch, and bumped the ebuild to ensure people pick up the fix. Best regards, Stu Closing bug |