So, we've got apache, which is the second most popular tag on the site.
It's a superset of the versions of it - apache2, apache2.2, apache1.3; and apache2 is essentially a superset of 2.0, 2.2, and soon to be 2.4; certainly, most of the apache2 questions are referring to version 2.2 and not 2.0.
Adding to that the company-vs-product naming; the internet community is perfectly content to call it Apache, while the Apache Software Foundation calls it "Apache HTTPD" or "Apache HTTP Server" these days - they don't want to give the impression that it's their only software, I guess!
I don't think something like apache-httpd-2.0 etc. would be sane or reasonable, but we should probably have some discussion on how to handle these tags. Any guidance on the "right" way to structure these on mSO?
Maybe crunch the 2.x tags all into apache2 in the same way that, say, the service packs for Windows Server tags don't merit their own tag? Or make apache2 a synonym of the current version (so make it synonym to apache2.2 right now, then to 2.4 once it's out and gaining traction)? And what of apache?
apacheas a tag, like we've banned
vmwareand force users into
apache*wildcards work almost everywhere you would expect them to...