New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
www-servers/lighttpd: refresh configs #35790
Conversation
Pull Request assignmentSubmitter: @gstrauss www-servers/lighttpd: @thesamesam Linked bugsNo bugs to link found. If your pull request references any of the Gentoo bug reports, please add appropriate GLEP 66 tags to the commit message and request reassignment. If you do not receive any reply to this pull request, please open or link a bug to attract the attention of maintainers. In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Should I also add |
Pull request CI reportReport generated at: 2024-03-16 23:34 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Glenn, thank you again for your help with lighttpd packaging. It's much appreciated.
Ah, good spot. How useful do you feel it is? Is it worth us supporting it unconditionally, or should we make it optional via a USE flag? |
libdeflate is more performant, but likely uses more resources. To give people the option, it should probably be a USE flag. |
I added a commit (untested) to attempt to add USE_LIBDEFLATE. Should I add put the changes in this PR made to www-servers/lighttpd/lighttpd-1.4.75.ebuild into www-servers/lighttpd/lighttpd-9999.ebuild instead of www-servers/lighttpd/lighttpd-1.4.75.ebuild ? Also, there is an ongoing discussion about mime.types in https://bugs.gentoo.org/show_bug.cgi?id=399401 I am looking for guidance on whether or not to include the change to www-servers/lighttpd/files/conf/lighttpd.conf-r1 to use the lighttpd builtin mimetype.assign list or to continue using the manual list compiled by Alan in www-servers/lighttpd/files/conf/mime-types.conf |
8c1bf50
to
f8230b1
Compare
The commit to add USE_LIBDEFLATE appears to cause problems due to libdeflate not being available on s390, so I have removed the commit from the PR. error:
commit:
|
f8230b1
to
1630bb4
Compare
While looking at the logs, I see Is there a recommended way to address this? One option would be to remove USE_NETTLE from lighttpd and to unconditionally build lighttpd to use nettle for crypto functions (such as to compute SHA-256). Another option would be to rename USE_NETTLE to something else to give Gentoo build the option to select the crypto library used by lighttpd (nettle, mbedtls, wolfssl, openssl, gnutls, nss). In practice, the choice is usually between nettle, mbedtls, and wolfssl if trying to build lighttpd as small as possible and using mbedtls or wolfssl for TLS (and for crypto functions such as to compute SHA-256). |
Pull request CI reportReport generated at: 2024-03-18 21:27 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
I do not see any packages outside /dev-perl/... with a version restriction on virtual/perl-Test-Harness. Should I select a random version to quiet this noise from the output report? |
* test configs with -tt for a better preflight config test. * graceful restart using SIGUSR1 Signed-off-by: Glenn Strauss <gstrauss@gluelogic.com>
* use https://wiki.lighttpd.net/ links to lighttpd wiki doc * add dev-db/sqlite dependency which is used by mod_webdav * remove e2fsprogs; mod_webdav no longer uses uuid_*() from e2fsprogs * remove libev; no longer used by lighttpd lighttpd directly uses native event frameworks (e.g. epoll) * remove 2+ year old deprecation warning trace * remove reference to lighttpd2; no lighttpd2 production release planned Signed-off-by: Glenn Strauss <gstrauss@gluelogic.com>
* remove obsolete modules * update syntax and comments Signed-off-by: Glenn Strauss <gstrauss@gluelogic.com>
* use lighttpd builtin mimetype.assign by default (can be overridden) x-ref: https://bugs.gentoo.org/399401 gentoo#19507 Signed-off-by: Glenn Strauss <gstrauss@gluelogic.com>
Signed-off-by: Glenn Strauss <gstrauss@gluelogic.com>
@thesamesam ping: please review when you have a chance
Thanks! |
Pull request CI reportReport generated at: 2024-05-04 05:24 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Thanks, sorry for the delay, and appreciate your patience. Let me try get to this today.. |
OK! I've rebased it on master where I got newer lighttpd stabled (had to backport the sparc patch from git), cleaned up old, and then also made your changes start with a new revision in ~arch/testing (to not change existing versions). I've hopefully done that right, but if I didn't, it's my fault, and not yours. I'll note in the commit message I mangled them. |
Don't worry about this for now. We're trying out a new QA check for Perl packages to remove deps where they're not very useful because they're dual-life Perl modules where no new version is needed. |
For this, let's put libdeflate in (in a followup/force-push once I push the changes I've got queued locally now), but drop ~s390. Then I'll file a rekeywording bug once the PR is merged (https://devmanual.gentoo.org/keywording/index.html#keywording-on-upgrades). |
Yeah, you're absolutely right. This is why I like having live ebuilds. It makes it way easier to see the diffs of changes. We should add one in.
Is it okay if we consider this together with the libdeflate changes? I don't want to hold up the rest of your improvements, but my head is somewhat fried for the rest of the day.
My inclination is to merge your PR's changes as-is for now, and then I think we should later move to generating from mime-types, and maybe put a comment in the ebuild describing how people can opt-out if they want a tiny embedded build... |
lighttpd-1.4.75.ebuild
lighttpd directly uses native event frameworks (e.g. epoll)
lighttpd.initd, lighttpd.service
-tt
for a better preflight config test.lighttpd.conf
@thesamesam please review when you have a moment