module naming scheme about httpd24u HOT 3 CLOSED

If you guys are gonna build mod_php against httpd24u now, I'm all for it 👍

For me personally it's not an issue (name change), but I would love to hear if somebody thinks he'll have problems adapting....

I would personally chose between:

python35u-mod24u_wsgi
httpd24u-mod_wsgi35u

First one may be confusing with 24u after mod, but second may be similarly confusing with what does 35u mean. So, I would go with first one. httpd24u for httpd package and xxx-mod24u_ for modules seems like a best combo. So final answer:

python35u-mod24u_wsgi

Other two not mentioned here seem to stand out too much....

from httpd24u.

+1, the httpd-%{verison} prefix would make it foolproof to identify the relevant supplementary packages.

from httpd24u.

We decided that the most important thing here is to improve discoverability for our users. As such, in the 2.4.20-2.ius release of httpd24u we have renamed the module subpackages.

Users will now see the IUS package when searching by the stock name, i.e. yum search mod_ssl. The packages have obsoletes to allow clean upgrades, and provide the old name so that running commands such as yum install mod24u_ssl will still work.

from httpd24u.