#45921 closed enhancement (fixed)
mod_jk: add apache24 variant
| Reported by: | girgen@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.2 |
| Keywords: | haspatch maintainer | Cc: | chrstphrchvz (Christopher Chavez) |
| Port: | mod_jk |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi!
This is a maintainer update. Could someone please commit?
Also, the simple fix in #45920 is required.
Attachments (1)
Change History (11)
Changed 9 years ago by girgen@…
| Attachment: | mod_jk-Portfile.diff added |
|---|
comment:1 follow-up: 2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Keywords: | haspatch maintainer added; apache apache24 mod_jk removed |
| Port: | mod_jk added; www/mod_jk removed |
| Summary: | [maintainer update] www/mod_jk -- add apache24 variant → mod_jk: add apache24 variant |
comment:2 Changed 9 years ago by girgen@…
Replying to ryandesign@…:
Hmm, I was not expecting us to add apache24 variants to anything. Rather, I was expecting the current contents of the apache24-devel port to replace the contents of the apache2 port and for the apache24-devel port to then disappear.
I don't mind that, in fact I totally agree, but it is sort of out of scope for the mod_jk port. =)
comment:3 Changed 9 years ago by kasperligaard+macports@…
Is there a plan for when the apache2 port becomes Apache 2.4 (instead of Apache 2.2)?
I am really hoping it will happen soon, escp. now that several major LTS distributions included it now.
PS: Sorry for asking here, but I don't know where to find the release process for Apache 2.2 -> 2.4 :-(
comment:4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
I don't have a specific plan or process in mind. If another developer wants to do it that would be fine.
comment:5 Changed 5 years ago by chrstphrchvz (Christopher Chavez)
Note that the current mod_jk +apache20 variant is now likely broken, since it has a path: dependency on apache20, which is obsolete.
comment:6 Changed 5 years ago by chrstphrchvz (Christopher Chavez)
| Cc: | chrstphrchvz added |
|---|
comment:7 Changed 5 years ago by Schamschula (Marius Schamschula)
We must have missed this one when obsoleting Apache 2.0.
comment:8 Changed 5 years ago by Schamschula (Marius Schamschula)
Note: The Portfile states Apache >= 2.1 contains mod_proxy_ajp which replaces mod_jk. We will make this port obsolete.
comment:9 Changed 5 years ago by Schamschula (Marius Schamschula)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:10 Changed 5 years ago by jmroot (Joshua Root)
What's the point of using the obsolete portgroup when there's no replacement? And why delete the whole port when only one non-default variant depends on apache20?
Hmm, I was not expecting us to add apache24 variants to anything. Rather, I was expecting the current contents of the apache24-devel port to replace the contents of the apache2 port and for the apache24-devel port to then disappear.