Slashdot Mirror
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."
The strangness that various distros impart to apache is why I usually start with Apache Toolbox. This uses wget to automatically download any missing source, and currently supports 60+ third party modules in addition to the 36 apache modules which are included in standard source distribution. For redhatters, this even halts appropriately for RPMs that cause problems. Works on slowaris, and pretty much any BSD/*NIX with gcc. I'm not a member of this project or anything, just a fan: it just works.
http://tinyurl.com/4ny52
NetBSD's ports patches most software as there are a few things that are specific to NetBSD. Just do a make install and watch it say 'patching...'. Minor things like LD_LIBRARY_PATH and things that if configure is not set up for then it wont find (not sure what their patches do). FreeBSD does the same thing. RedHat can't ship a default kernel they have to ship their own kernel. So what's the point? In order for any vendor to ship apache or any other software they usually have patches applied. This is because the way apache is setup to do things and the way that the vendors setup things is different. To get update and things you have to pretty much wait till they are ready to update the software.
Solution: You want a virgin apache, download the source from apache.org and compile and install yourself. Pass configure the options you want. It's really not that hard.... Is this really worthy news?
Only 'flamers' flame!
Apache is one of those programs that I actually refuse to use a binary distribution of. I just download the latest source, set my preferred options (making sure I build with dynamically loadable modules, which allows me to comment out the ones I don't need in httpd.conf) and away I go. If Apache is installed, I "rpm -e" it and then "make install" my source-built version. If I want to upgrade, usually only the httpd binary and modules need updating and then a quick restart of the server and I'm nicely up-to-date (would you trust "rpm -Uvh" on a live production server's Apache ??!).
that distributions are doing precisely what open source software was designed to permit.
Shock is expressed that all users of apache do not bow down to the demands of pencil pansies everywhere but that a free flowing and open marketplace of ideas expressed in different software variations exists.
In good news however, software users can find software that doesn't have many variations or 'dubious patches' at their local Office Depot in boxes produced by Microsoft.
Give me a break. This is news how?