#5550 closed enhancement (fixed)
UPDATE: lighttpd 1.4.8
Reported by: | brennan@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | High | Milestone: | |
Component: | ports | Version: | 1.0 |
Keywords: | Cc: | matt@…, jstetser@… | |
Port: |
Description
Please update port lighttpd to source version 1.4.6 at your convenience. http://www.lighttpd.net/download/
Per the changelog, it includes compilation fixes for mac os x among other fixes.
Thank you.
Brennan brennan@…
Attachments (4)
Change History (16)
comment:1 Changed 19 years ago by mww@…
Owner: | changed from darwinports-bugs@… to jstetser@… |
---|---|
Summary: | update port lighttpd → UPDATE: lighttpd |
Changed 19 years ago by luc@…
Attachment: | Portfile.diff added |
---|
Changed 19 years ago by jstetser@…
Attachment: | lighttpd-1.4.7.tar added |
---|
Portfile for Lighttpd 1.4.7 with ssl and mysql variants, includes lighttpd.conf file
comment:2 Changed 19 years ago by luc@…
As of today, lighttpd is now at 1.4.8. Hello ? Anybody there ?!??
comment:3 Changed 19 years ago by blb@…
Jacob, be sure that when you have an update to one of your ports that's ready to commit, to reassign the bug to darwinports-bugs@… so someone can commit it; I'll leave this one as is in case you want to update to 1.4.8 first...
Changed 19 years ago by jstetser@…
Attachment: | lighttpd-1.4.8_0.tar added |
---|
Portfile for Lighttpd 1.4.8 with ssl and mysql variants, includes lighttpd.conf file
comment:4 Changed 19 years ago by jstetser@…
attachments.isobsolete: | 0 → 1 |
---|
comment:5 Changed 19 years ago by jstetser@…
Owner: | changed from jstetser@… to darwinports-bugs@… |
---|---|
Summary: | UPDATE: lighttpd → UPDATE: lighttpd 1.4.8 |
Ready for committing.... I'd like to place the file in the archive in a fitting directory (/opt/local/var?) -- If I can find out how to do that I'll revise the patch to do so.
Thanks.
comment:6 Changed 19 years ago by matt@…
Cc: | matt@… added; toby@… removed |
---|
I don't want to be the annoying guy here, but why lighttpd.conf is included if it isn't installed on $ {prefix}? You're talking about "${prefix}/var", it's where you want to put the "file" (is the file you're talking here is lighttpd.conf)? If that so, configuration files are better placed in "${prefix}/etc/" (even "${prefix}/etc/${portname}"). My 0,2¢.
I will gladly commit it, if Bryan doesn't do it first, but first please review your port. Thanks Jacob.
comment:7 Changed 19 years ago by JLM939@…
Cc: | mww@… added |
---|
Matt, Brian, et al:
Would one of you be so kind as to go ahead and commit version 1.4.8 as soon as possible?
Matt: I agree that ${prefix}/etc/lighttpd/lighttpd.conf is probably the best location for the bundled lighttpd.conf file. However, given that it may take some time for Jacob to determine how to get DP to put the bundled lighttpd.conf file in the above location*, we shouldn't be holding up the release of 1.4.8 to all those people who need the new Lighttpd features -- people who may already have an extensive existing lighttpd.conf file. Can we please get 1.4.8 committed -- with or without the bundled lighttpd.conf file?
(*And what if lighttpd.conf already exists at that location? We don't want to
just overwrite it, so how does DP handle this?)
Finally, the Lighttpd page on DarwinPorts refers to 1.3.14 in the title, header, and intro text, and the portfile listed below is for 1.4.4. All should be updated for the 1.4.8 release. See the following link:
http://lighttpd.darwinports.com/
Thanks for listening! --Justin
comment:8 Changed 19 years ago by matt@…
(In reply to comment #8)
Matt, Brian, et al:
Would one of you be so kind as to go ahead and commit version 1.4.8 as soon as possible?
Matt: I agree that ${prefix}/etc/lighttpd/lighttpd.conf is probably the best location for the bundled lighttpd.conf file. However, given that it may take some time for Jacob to determine how to get DP to put the bundled lighttpd.conf file in the above location*, we shouldn't be holding up the release of 1.4.8 to all those people who need the new Lighttpd features -- people who may already have an extensive existing lighttpd.conf file. Can we please get 1.4.8 committed -- with or without the bundled lighttpd.conf file?
As soon as Jacob finds what he wants to do with lighttpd.conf, no problem. And if he needs help about his portfile, darwinports@… is the place to go.
(*And what if lighttpd.conf already exists at that location? We don't want to
just overwrite it, so how does DP handle this?)
Jacob could rename the new lighttpd.conf to ${prefix}/etc/${portname}/lighttpd-${version}.conf This wouldn't damage any existing lighttpd.conf
Finally, the Lighttpd page on DarwinPorts refers to 1.3.14 in the title, header, and intro text, and the portfile listed below is for 1.4.4. All should be updated for the 1.4.8 release. See the following link:
darwinports.com isn't the official DarwinPorts website. Please stop using it as a reference, it provides erroneous informations. As for the current lighttpd port, we're at version 1.4.4. See the following url for more information:
<http://darwinports.org/ports/?by=name&substr=lighttpd&Search=Submit>
Thanks.
comment:9 Changed 19 years ago by JLM939@…
(In reply to comment #9)
Would one of you be so kind as to go ahead and commit version 1.4.8 as soon as possible?
As soon as Jacob finds what he wants to do with lighttpd.conf, no problem. And if he needs help about his portfile, darwinports@… is the place to go.
I have contacted Jacob separately via email and asked him to respond to this ticket, in hopes of getting 1.4.8 committed as soon as possible.
I have to say that I think that something appears to be broken with this process. A few days -- even a week -- of time delay after a new Lighttpd release would be understandable. But three months? And why? Because a maintainer isn't sure how to place a (highly optional) file in the right place? I'm not trying to be antagonistic; on the contrary, I'm asking for creative suggestions as to how we can solve this problem.
(*And what if lighttpd.conf already exists at that location? We don't want to
just overwrite it, so how does DP handle this?)
Jacob could rename the new lighttpd.conf to
${prefix}/etc/${portname}/lighttpd-${version}.conf
This wouldn't damage any existing lighttpd.conf
That sounds like a great idea. I wish some of the other port maintainers would follow a similar convention.
Finally, the Lighttpd page on DarwinPorts refers to 1.3.14 in the title, header, and intro text, and the portfile listed below is for 1.4.4. All should be updated for the 1.4.8 release. See the following link:
darwinports.com isn't the official DarwinPorts website. Please stop using it
as a reference, it provides
erroneous informations.
Duly noted. Thank you for the clarification.
As for the current lighttpd port, we're at version 1.4.4. See the following
url for more information:
<http://darwinports.org/ports/?by=name&substr=lighttpd&Search=Submit>
Yes, I'm painfully aware that we're currently stuck at 1.4.4 -- a situation I hope we can resolve soon. :)
comment:10 Changed 19 years ago by jstetser@…
I haven't been receiving these bug reports, oddly enough.
I just emailed the darwinports list to get help on installing the lighttpd.conf file in
${prefix}/etc/${portname}/lighttpd-default.conf
As soon as I have a solution, I'll make the changes, upload the final version of the portfile, and send it along to be committed.
Jake
Changed 19 years ago by jstetser@…
UPDATE: lighttpd-1.4.8 now with conf-file kung fu action
comment:11 Changed 19 years ago by jstetser@…
attachments.isobsolete: | 0 → 1 |
---|
comment:12 Changed 19 years ago by matt@…
Cc: | jstetser@… added; mww@… removed |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Committed. Thanks Jacob!
Portfile diff for lighttpd 1.4.7