Virgin Apache is Hard to Find

markcox writes "Apache Week had written an article examining the Apache packages distributed by 10 popuplar Linux vendors. The survey found that all the vendors added some patches to virgin Apache including build patches, backported security patches, changing the product name through to dubious patches, and missed security fixes."

Comments

open source

[charmer]

From the article: "The Apache Software Foundation would rather that vendors of Apache didn't add any third-party modifications to Apache at all - it adds to brand confusion. It's rather like going to buy Coke, complaining to the Coca-Cola company that the drink was too sour, then finding that your supermarket was adding lemon."

Thats because Coke is not open source. Isn't the ability to modify an inherent feature in open source software ?

Charmer

Re:open source

[jericho4.0]

True, but the Apache team does have a valid concern, in that people who think they're getting vanilla Apache are getting something else.

I think a good compromise would be every dist including comprehensive changlogs.

Re:I just compile from the source

[DA-MAN]

I sure do, it's easier when you have to update many servers to set up a local rpm site and have all servers update. The main thing is to roll your own Apache rpm. which is not too hard

Re:"virgin" httpd set up easier with ApacheToolbox

[peterdaly]

I have to second that. ApacheToolBox rocks. Not only can it download and configure all of that, but it can also create an RPM at the end that contains everything and the configuration.

That's a nice feature when you want the exact same configuration on more than one server.

-Pete