Package naming about ea-apache2-bluehost

[karljohns0n]

IMO the improvement of having a different package of the patched apache would the possibility to integrate it easily in EA4 without adding a new/custom repository. If you choose the package with the patch in EA4 (ie: ea-apache24-patch), it will conflict with ea-apache24 and will install the patched apache (by setting the Conflict and Provides in the spec). You could also use yum swap as I said to swap between the standard and patched apache. This way, cPanel customers could still use this patch with EA4 for those who cannot workaround the issue with the kernel. It would be good to see if you have any stats of your customers who use this patch in EA3 to confirm if it's worth it.

[HoustonDad]

Hi Karl,

I see where you're coming from. There are no plans right now to integrate this module upstream with EA4, so this is the best we get right now :)

[karljohns0n]

Ok, too bad :) My suggestion was a way to keep this EA3 patch in EA4 to make EA4 migration easier. Packages in a custom repository outside EA wont be used by customers as it wont be officially supported nor integrated in the UI. I'll keep watching the changelog to see if it gets included in the futur. Thanks!