In net-analyzer/munin, the USE flag 'apache' is taken to mean "install the apache configuration template". For other ebuilds that come to my mind (php, subversion), this is accomplished with the 'apache2' global USE flag. So to adhere to the "principle of least surprise", I propose to rename the 'apache' USE flag in net-analyzer/munin to 'apache2'. I'm willing to provide a patch, can anyone give me a hint / working example in another ebuild for code that Does The Right Thing (TM) WRT notifying the user about the change?
We could equally well argue that the "apache2" USE flag should be renamed "apache".
(In reply to comment #1) > We could equally well argue that the "apache2" USE flag should be renamed > "apache". I certainly won't dispute THAT motion ;-) Since at least 2005 I felt the appended version number to be somewhat artificial. ... and there's only 28 ebuilds in the tree that use 'apache2' now. I would have thought that to be a *lot* more; therefore I didn't even consider that alternative. Besides munin, there is one other package (dev-lang/v8cgi) that uses 'apache', and it's used to enable apache integration as well. So no conflict there. Is there an established procedure to rename a global USE flag?
bump, vote for rename
The USE flag has been changed to apache2 in munin 2.0.33-r1.
